Abstract
Testing is a crucial stage not only in software development but also in every other industry. The clothes we wear, the food we eat, the toothbrush we use, even in this pandemic time (no pun intended) everything goes through some or other kind of testing to ensure product safety, quality, and our trust in companies.
Practically, the number of test cases even for a small piece of code or software could be infinite. Thus, stakeholders and the QA team generally agree upon the cases which are feasible to cover in a given timeline.
It is not practically possible to cover a large number of test cases manually. Eventually, teams started to automate the tasks which are repetitive and could be abstracted to run for future developments. This saves time for some complex testing scenarios which are not easy to automate. Also, it gives an assurance to stakeholders that the quality of testing is uniform across all the test cases. This combined with automated deployment led to Continuous Integration/Continuous Delivery (CI/CD). CI/CD has improved the development cycles to great extent by reducing the responsibilities of manual deployment and unit testing. In addition, it has reduced the time to the market and has given confidence to stakeholders before each release. Today we will see how we can automate the test cases with Selenium, TestNG, and Adobe Experience Manager.
Read Full Blog
Q&A
Please use this thread to ask the related questions.
Kautuk Sahni