In software development, we understand very well the importance of testing. While writing unit tests is considered widely popular and common, unfortunately, they don’t provide the full coverage needed for the entire software.
The better approach is End-to-End testing as a part of the testing routine during development. In fact, End-to-End testing is considered the holy grail, the trophy in the Testing Trophy, or the top of the Testing Pyramid because they tend to be harder to implement than the rest of the testing types. But End-To-End tests can be quite complex and require a well defined infrastructure that is much harder to implement and maintain.
An example of a quote type content, an example of a quote type content, an example of a quote type content, an example of a quote type content
Main title in an article / blog / case study
As an early-stage startup, Swimm initially worked in one-week sprints that ended with a new release. The day of the release would start with manually QA-ing the entire app, doing all kinds of user flows to make sure everything worked and no regression bugs were discovered.
Secondary title in an article / blog / case study
As Swimm grew, more developers joined the company, and as we began adding many new features, it was increasingly harder to keep up with the changes. The number of regression bugs that were created during each sprint grew in leaps and bounds; finding the cause of each bug became a nightmare; spending a whole day just for fixing regression bugs (out of a 1-week sprint) seemed like an inefficient use of our time – time that could be well spent on developing many more new Swimm features.
Paragraph containing an image content example
As Swimm grew, more developers joined the company, and as we began adding many new features, it was increasingly harder to keep up with the changes. The number of regression bugs that were created during each sprint grew in leaps and bounds; finding the cause of each bug became a nightmare; spending a whole day just for fixing regression bugs (out of a 1-week sprint) seemed like an inefficient use of our time – time that could be well spent on developing many more new Swimm features.
Numbered / Bullet list content type example:
- Easy – most developers don’t write E2E tests or have loads of extra time; the E2E testing devtool needed to be easy to use.
- Intuitive – we already speak several languages; we needed an intuitive E2E testing tool without needing to learn a new language or complex API.
- Maintainable – with no automation engineer on the team, we needed a product with minimum setup and no complex infrastructure.
- First bullet point example
- Second bullet point example
- Third bullet point example with an extra long paragraph that cuts into two lines in the middle of the sentence with secondary bullets:
- Secondary bullet point style
- Secondary bullet point style
- Secondary bullet point style
