Tag - automated test

How to start UI automated tests with Playwright

The advantages of using Playwright for UI testing?

In the modern trends of web applications development the great advantage is to have an opportunity to create automated tests quickly, launch them and get representative execution results for the analysis. That’s why to achieve it and gain the edge over the popular webDriver and Chrome DevTools protocol technologies, Microsoft started its open source project Playwright, which provides QA engineers with following features in UI automated testing:

Read More

The benefits of using an offshore software development company for your business

In the last few years, outsourcing has become a successful and widespread business strategy, with enterprises only using internal staff for core business functions while asking external actors to complete an array of secondary tasks. The outsourcing industry represents 31% of IT services in the world, and the global outsourcing market generated an average of $92.5 billion in revenue between 2000 and 2019 (Statista).

Read More

Mobile automation testing. To use or not to use?

To use or not to use – every customer asks themselves this question, when it comes to mobile automation testing. They say that development and supporting of UI auto tests costs too much. But let’s return to the statement a little bit later. And now we are going to discuss the following questions: what is mobile automation, who is it for, what for and do you actually need it?

Read More

Automated Tests: Why and How

If you aren’t implementing a prototype for some quick demo in some 8 hours, 3 days, etc. to archive it in a folder like the “trash” right after that, then you will have to think about the quality assurance, finding bugs, etc. Somebody will have to do this job after all. Whether you include the automated tests in the code development process or you totally rely on the testers, the automated tests will appear in your system sooner or later (or the project will die aborning).

The worst thing is that auto tests are also the code, i.e. all problems relating to the code development (the design, bugs, usability, performance, etc.) exist in tests. When you automate the testing, you actually implement the new functionality in your system. Thus, you should develop tests as any other features.

Read More