Bot preaches

So, we have concluded on the test cases to be automated. Next step is to find out what framework fits our requirement of the project. Automation framework is a set of rules or guidelines one must follow to automate the testing process. Its simply a way of defining what fits where. The determining factor for choosing the framework is how our testing works. This will be defined in the test strategy in the test plan of a release. We can classify the frameworks in to Record and Playback 1. Record and Playback : Simple form of automation. It records the users actions and plays back them. Application is expected to have same variables every time the playback is run. Comes with the disadvantage that objects on the page cannot change no matter what. 2. Library architecture framework: There is a main "driver" class or file that accesses the remembered objects on the page or objects from POM, libraries, data files, utils and property files. The driver mocks the user...

When you are working on a project, generally test cases become thousands in number within a very few releases. How do you manage those and how will you decide which ones to repeat in your next releases? Assume you developed 3 modules newly. Each module is having 50 test cases which you ran in the sprints of development of feature functionality testing cycles Here are some of the hints to decide upon the reuse ability of the test cases. Do's: Test those modules which use the same code as the newly developed modules Choose the test cases of basic operations on the modules Use tagging to tag same test cases for feature functionality testing as well as regression testing Choose all the corner cases of testing Test for special type of data Test those cases which were broken in the earlier testing cycles Test with different types of user logins(Customer, Admin, Super Admin) Test functionalities that send emails Test functionalities that are run through cronjobs ...

Let me begin the blog by letting all you know what prompts a tester to automate the test cases. There is a module to be tested and you write test cases, execute them and happy with the results, your job is done. Ask some of these questions here: 1. Will these test cases be executed anytime again? 2. How frequently should you be executing them? 3. Who will execute them next time? Once you have the answers, lets dwell on to deciding how automation can help. If you have Multiple rounds of testing like feature functionality testing, regression testing etc in the same release cycle Execute the same test cases in future releases regression suites Test cases with varying test data Scenarios of complex flows, its good to automate them which will give you the ease to jump in a particular step without executing the previous steps manually Many types of users doing same action and you need to make sure your application works fine for each one of type of login Multiple brow...