Very good article. The definitions of test is important just to keep everyone, but mostly managers on same page. Today; however those definitions are blurred. Why? Because the tooling has vastly improved. Selinium being the first, but it's been superceded by Cypress and Puppeteer. This means the traditional definitions are outdated. For example, If we can intercept and alter all inbound and outbound Http requests what definition of test does that become? It's closer to Functional testing but is done at same layer as E2E tests. If we look deeply into Karma and Jasmine we find a major tooling restriction, no outbound requests happen due to poor design this means the Unit Tests are crippled. Everything needs mocking.
Cypress overcomes all these hurdles and blurs the legacy test definitions.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very good article. The definitions of test is important just to keep everyone, but mostly managers on same page. Today; however those definitions are blurred. Why? Because the tooling has vastly improved. Selinium being the first, but it's been superceded by Cypress and Puppeteer. This means the traditional definitions are outdated. For example, If we can intercept and alter all inbound and outbound Http requests what definition of test does that become? It's closer to Functional testing but is done at same layer as E2E tests. If we look deeply into Karma and Jasmine we find a major tooling restriction, no outbound requests happen due to poor design this means the Unit Tests are crippled. Everything needs mocking.
Cypress overcomes all these hurdles and blurs the legacy test definitions.