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. Continue reading →
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”. Continue reading →
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.
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.
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.
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.
“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 Continue reading →