Shulou(Shulou.com)06/03 Report--

The following is a list of guidelines and tips for software testers and QA professionals to participate in testing applications. These software testing techniques come from years of experience in testing Web applications in an agile environment. If you want to share test tips, add them to the comment field.

QA guidelines for testing stories / errors

-Don't leave any unanswered questions. The acceptance criteria must be complete to ensure that you fully understand what the function / story is trying to achieve.

-make sure you know how to test features / stories.

-when considering test cases, consider the complete end-to-end process.

-consider all related error conditions, such as Web service disconnection, invalid input, etc.

-consider different browsers-depending on the supported browsers.

-consider the impact of mobility-mobile networks and tablets-does any feature behave differently when used on a touch device than using keyboard navigation?

-consider the basics of security testing, such as URL and resources in protected areas of the https website.

-consider whether this story needs to be included in the automated test suite.

-as a rough guide: only cases that cause P1 or P2 to fail during its production will be automated. This also includes scenarios where a large amount of data needs to be checked, which can be a very repetitive manual operation.

-when you find errors related to the story, promote them as error subtasks to ensure that the link to the story is maintained.

-when signing a story or error when completing a test, be sure to add comments in the Jira, including the test environment and version of the code that the test signed.

-if the story or error cannot or will not be tested by QA and will be tested by the developer, make sure you review the test method and add a comment in the Jira that you approve the developer's test method, preferably a short description. Make sure that the version being signed is added to dev.

About daily tasks

-understand the application area that the developer is modifying

-what unit tests have developers written?

-what is a high priority story and work first according to the sprint day

-clarify a vague story

-check automatic check to see if there is any fault

About Sprint Planning

-estimate the test for each story

-talk to PO to resolve any misunderstandings about the new story

-make sure the story is testable.

-the idea of getting a test by asking questions was very proactive in the meeting.

-start thinking about advanced test scenarios

Work with Dev and PO on test design

-consider test cases to verify functionality, apply various testing techniques, positive, negative, boundary values, equivalent partitions, etc.

-use Mindmaps to assist in testing scenarios and user journeys

-consider risk-provide more test conditions around high-risk characteristics

-when designing test cases, always consider "if", "what else" and "what else"

-consider integration testing, how this feature affects the nearest neighbor function

-really understand what happens when you interact with features, not just look at them from the surface. Think of the back-end system / database / Web service you are touching

-candidates for automation-which test cases are best automated

-when there are many data combinations to test, how to reduce alignment without affecting quality / testing-such as using pairwise testing techniques

-Peer review test conditions-discuss designed test cases with the developer

About test execution / completion

-pre-execution test environment / prerequisite settings

-testing can be carried out when the function is ready.

-ensure that quick feedback is provided to developers

-check automatic check to see if there is a fault

-whether the newly developed features make commercial sense

-talk to developers to improve the testability of features

-if the workflow changes, be sure to update the existing test

-maintain test packages and ensure that all tests are up to date

On process improvement / self-development

-understand the new development of software testing

-what is the current problem with the QA process? How to solve and improve the current problems

-learn database, coding, Web technology and other technical skills in order to better understand what happens during testing

-discuss their views on process improvement with the team

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.