QA Test Automation
The topic of automation is not new, there are still extreme opinions around. Some argue that you need to automate everything, others that they do not see any sense in this activity as it is an additional cost of systems development that never pays off. TWG experts know how to find the balance so that the tests are not only an artificial artefact, but something that improves the development process and contributes to the better quality of your products. Qa automation is a complementary to DevOPS Factory CI/CD activities bringing pipelines to yet another level.
QA Test Automation in a distributed microservices environment is no longer an option. If you want to eliminate the fear of change for your developers and pain of change for your stakeholders you should not diminish the importance of this part.
You need functional tests for your API, UI or performance. If you already have your own development and quality problems or you plan to start development considering quality as the top goal, then you are in the right place.
Do you still think that the continuous deployment process is reserved only for large players and it is impossible for features implemented during the sprint to go straight to production, avoiding the tedious (manual) verification process? If so, let us prove you wrong.
a little bit text