Software Testing – Practical Tips for Software Testers

  1. Home
  2. Kochi
  3. Blogs
  4. Blogs

Following are the Guidelines for Software Testers and QA Professionals when it comes to testing applications. These software testing tips introduce a Web site for years from the tail experiments. If you'd like to share your test tips, add it to the comments field.

Some Guidelines for QAs when Testing for Story / Bug

  • Do not give up any questions that are not answered. Authentication criteria must be completed in order to fully understand what they want to achieve about feature / story.
  • Make sure you know how the feature / story is tried.
  • Consider the complete ending of the case when considering the test cases.
  • Consider all related error situations, e.g. Web service connection down, invalid inputs, etc.
  • Consider different browsers depending on supported browsers.
  • It's like using a keyboard to navigate, working differently on any specifications when using the touch device - mobile web and tablet
  • Consider the security checking requirements, such as the Https 2 URL, sources for the site's protected areas.
  • Consider whether these story warrants should be included in the automatic test suite. As a rough guide: Only the conditions that may result from P1 or P2 in the production will be automated. It needs to be checked with lots of data, which can be very repetitive to manually.
  • When the bugs associated with a story are found, assemble them as bug-slabs, and ensure that the link to the story is kept.
  • When testing is complete when a story or bug is off, make sure to leave a comment in a gir, including the experimental environment and code version of the tested off.Review or ensure the approach of the exam if a QA is not tested or a QA is tested or a developer has been tested instead. A brief description. Debate which version to sign off.

In daily tasks

  • Learn the area of ​​the modified app for developers
  • What developers wrote about unit checks
  • What stories are high priorities based on Sprint days
  • Get clarification on obscure stories
  • Review automatic checks to check if there are any failures

Sprint Planning

  • An approximate test of every story
  • Talk using PO to solve the misunderstandings in new stories
  • Make sure the stories are experimental
  • Asking questions to receive ideas in the exam is very encouraging
  • Start thinking about the high-end experimental possibilities

On Test Design in collaboration with Dev and PO

  • Features Check Value, Various Test Techniques, Positive, Negative, Boundary Values, Equation
  • Use Mindmaps to help test moments and user trips
  • Consider the risks - more test conditions around a feature of high risk
  • Always think about "what to do", "something else", "how about something" when designing the case cases
  • When checking multiple additions to trials, how to reduce permits without compromising in quality / verification - e.g. Using a pair of expert test methods
  • Peer Reviews on Test Levels - Discuss with developers with test cases designed

In test execution / completion

  • Test conditions / advance setup before executing
  • Check immediately if a feature is ready
  • Make sure to give quick feedback to developers
  • Review auto-tests to check if there are failures
  • Test conditions / advance setup before executing
  • Check immediately if a feature is ready
  • Make sure to give quick feedback to developers
  • Review auto-tests to check if there are failures

Process Improvement / Self Development

  • Learn about new developments in software testing
  • What are the current issues of the QA process / can solve and improve the current issues
  • Learn technical skills like databases, code and web technologies to better understand what's going on during testing
  • Talk to the team about the progress of the process