Learn how to use Software testing templates. We have covered different QA templates in excel and MS document format. Test case, test plan, daily status etc.
In today’s article we are going to learn all about the “Incident Tracking and management” Process – How to track and manage incidents in Software Testing with sample templates.
Are you thinking- “STH has published a lot of content on defect/bug tracking, so how is this going to be different”? That is exactly the reason why we have to look at what we mean by incident first.
Let’s see the typical process involved in delivering software from ‘development phase’ to the ‘testing phase’ for a successful bug-free software release to production/client.
These processes are either overlooked or skipped by software companies, which results in poor test management and thereby’ a “buggy” software releases to the client, which leads to “unsatisfied customers”.
Read moreHow to Improve the Test Release Process for Successful Bug Free Software to Production
Several documents and reports are being prepared as part of Testing. Some are Test Strategy doc, Test Plan doc, Risk management Plan, Configuration management plan etc. Among these Test Summary Report is one such report which is prepared after the Testing is completed.
I have tried to explain the purpose of ‘Test Summary Report’ and provided a sample Test Summary Report template along with an actual report for download.
What is a Test Summary Report?
This is the concluding part of our “software testing training on a live project” series.
It is going to be about defects and also few remaining topics that will mark the completion of Test execution phase of the STLC.
In the previous article, while Test Execution was going on, we encountered a situation where the expected result of test case was not met. Also, we identified some unexpected behaviour during exploratory testing.
What happens when we encounter these deviations?
Read moreLive Project Bug Tracking, Test Metrics, and Test Sign off – Free QA Training Day 6
Just to rehash what we have been doing so far – we are working our way through the Software Testing Training mini-course on a live project OrangeHRM.
In this free online QA training series so far, we are done with:
Now, we have reached the part that is the real deal, the test cases.
An Ultimate Guide to Software Test Plan Document:
This tutorial will explain you all about Software Test Plan Document and guide you with the ways on how to write/create a detailed Software testing plan from scratch along with the differences between test planning and test execution.
Live Project QA Training Day 3 – After introducing our readers to the live application of our free online software testing training, we came to know how to review SRS and write test scenarios. And now it’s the right time to dive deeper into the most important part of the software testing lifecycle – i.e. Test Planning.
Read moreTest Plan Tutorial: A Guide to Write a Software Test Plan Document from Scratch
This is the second tutorial in our ‘free online software testing training on a live project’ series. If you are new here please check the first introduction tutorial: End to End Software Testing Training on a Live Project.
Let us now get into a detailed analysis of how an SRS walkthrough happens, what is it that we need to identify from this step, what pre-steps we need to take before we begin, what are the challenges we could face etc. in a detailed manner.
SDLC’s Design Phase:
Software QA Testing Checklists:
Today we bring to you another quality tool that is so often underused that we thought we would rehash details about it in the hope that it regains its lost glory. It is ‘Check List’.
Definition: A checklist is a catalog of items/tasks that are recorded for tracking. This list could be either ordered in a sequence or could be haphazard.
Checklists are part and parcel of our daily lives. We use them in various situations from grocery shopping to having a to-do list for the day’s activities.
Read moreThe QA Software Testing Checklists (Sample Checklists Included)
What is Requirements Traceability Matrix (RTM) in Software Testing: Step-by-step guide to creating Traceability Matrix with examples and sample template
Today’s tutorial is about an important QC tool, that is either over-simplified (read overlooked) or over-emphasized – i.e Traceability Matrix (TM).
Read moreHow to Create Requirements Traceability Matrix (RTM): Example and Sample Template
Software Testing Status Reporting:
“The agreement that a certain information, in a certain format, will be sent by a certain team/individual, at certain intervals of time, to certain members – is like a handshake- an acknowledgement that no matter what the outcome of a task at hand, you would be kept posted about it, sooner than later.”
This is the first section of an IT professional’s oath. Well, I’m kidding! There is no oath, but if there was one, this would surely top the list of items in it. Isn’t it?
Accountability and transparency (A & T) are essential to every IT project at various levels – Project level, team level, task level and also individual
Read moreHow to Report Test Execution Smartly – [Download Status Report Template]