Discussing the difference between a test plan and a test strategy explaining when should you use a plan, and when is it better to use a strategy
Testers are always the backbone of a project. For a tester to play multiple roles and to do their work efficiently they must have some unique qualities.
Scriptless Test Automation enables testers and business users to automate test cases without worrying about the coding. It helps to achieve faster results and reduces the time expended to understand and develop the code leading to faster TTM higher ROI and increased coverage with low maintenance.
Testing in Machine learning is way too different from the way we test software traditionally(functional tests regression tests etc.) where we check for actual vs expected behavior of any given application. In the ML world data sets with desired behavior are used to train the model(learn the logic) and we need to check if the trained model consistently provides us with the expected output.
Sharing my work experience moving from the Dominican Republic to the USA. From being Regional QA lead for Transunion Latam to working at Chipotle.
The excellent bug report raises the issue and provides sufficient data for a good decision.The article describes why do programmers do not fix some bugs so how to report bugs accurately so that the reader understands the impact of the problem and takes up for fix.It describes RIMGEN a guide for how to investigate bugs and communicate better.It also describes about some good Bug reporting skills for a Tester to improve his credibility.
Regression testing is always an integral part of any software development life cycle. If we plan, design and strategise our testing well before, we can definitely achieve less painful and better coverage in regression testing during sprints as well as in final release. Our Synapse Dhanalaxmi shares about Regression Testing strategy in sprint.
A test plan outlines the approach for testing a specific feature before it is delivered to the customer. There are folks who take a different approach to creating test plans depending on factors like business needs, based on automation frameworks available and the metrics to be measured. By considering Netflix subscription and cancellation as an example I am sharing my thought process for creating a test plan.