Skip to main content

iTesting : Software Testing Life Cycle

Image
By
Software Testing Life Cycle (STLC) defines the steps/stages/phases in testing of software. However, there is no fixed standard of STLC in the world and it basically varies as per the following:
Nevertheless, Software Testing Life Cycle, in general, comprises of the following phases:
Software Testing Life Cycle
PhaseActivityDeliverablesNecessity
Requirements/Design ReviewYou review the software requirements/design (Well, if they exist.)
  • Review Defect Reports
Curiosity
Test PlanningOnce you have gathered a general idea of what needs to be tested, you ‘plan’ for the tests. Farsightedness
Test DesigningYou design/detail your tests on the basis of detailed requirements/design of the software (sometimes, on the basis of your imagination). Creativity
Test Environment SetupYou setup the test environment (server/client/network, etc) with the goal of replicating the end-users’ environment.
  • Test Environment
Rich company
Test ExecutionYou execute your Test Cases/Scripts in the Test Environment to see whether they pass. Patience
Test ReportingYou prepare various reports for various stakeholders.
  • Test Results (Final)
  • Test/Defect Metrics
  • Test Closure Report
  • Who Worked Till Late & on Weekends Report
Diplomacy
Interestingly, no matter how well-defined a Software Testing Life Cycle you have in your project or organization, there are chances that you will invariably witness the following widely-popular cycle:
  • Testing
  • Cursing
In this type of STLC, you skip phases like requirement/design review, test planning, and test designing –in the high hope that the skipping will save you some time and/or cost.
Also, note that the Software Testing Life Cycle phases mentioned above do not necessarily have to be in the order listed; some phases can sometimes run in parallel (For instance, Test Designing and Test Execution). And, in extreme cases, the phases might also be reversed (For instance, when there is Cursing prior to Testing).

Source : Read Here

Thanks , Keep Coding :)
Labels:

Comments

  1. Jagran TodayOctober 21, 2013 at 4:24 PM

    Software Development life cycle is the process which is followed to develop a software product. It is a structured way of building software applications. Most organizations have a process in place for developing software; this process may, at times, be customized based on the organizations requirement and framework followed by organization.

    ReplyDelete

Post a Comment

Popular posts from this blog

WPF-MVVM: RelayCommand Implementation

By
In WPF if we are implementing MVVM pattern then we need to play with Command rather than Events. You can use ICommand interface to create each command class. Implementation of ICommand in a class gives you CanExecute(), Execute() methods which take part in the action performed by Command.   Rather than making Command Class for each Command we can implement a generic Relay Command to get Command. Below is a RelayCommand class that we will implement.   ///   <summary>      ///  To register commands in MMVM pattern      ///   </summary>      class   RelayCommands  :  ICommand     {          readonly   Action < object > _execute;          readonly   Predicate < object > _canExecute;  ...
Post a Comment
Read more

.Net List with Changed event

By
Sometimes we need a List which can notify user when an item is added. Here is the way that you can implement a generic ArrayList which notifies user at the time of an element is added.   using  System; using  System.Collections; namespace  ArchiveData.Logging {    // A delegate type for hooking up change notifications.    public   delegate   void   ChangedEventHandler ( object  sender,  EventArgs  e);    public   class   ListWithChangedEvent  :  ArrayList   {      // An event that clients can use to be notified whenever the      // elements of the list change.      public   event   ChangedEventHandler  Changed;      public   object  NewlyAddedItem {...
Post a Comment
Read more

What is DispatcherTimer in wpf?

By
DispatcherTimer When you want to set a timer working with GUI, you always come across threading problem. The problem is that if you want to send some changes to UI that is constantly/continuously changing then that will make your UI unresponsive or in other words it will hang your UI.   To overcome from this situation, WPF gives us DispatcherTimer threading functionality that will take care of such continuously changing processing on UI thread and that will not hang your UI. We can accomplish same scenario in Win Form , through System.Windows.Forms.Timer and in WPF it is System.Windows.Threading.DispatcherTimer .   Difference between DispatcherTimer and Regular timer (System.Timers.Timer) DispatcherTimer is the regular timer. It fires its Tick event on the UI thread, you can do anything you want with the UI. System.Timers.Timer is an asynchronous timer, its Elapsed event runs on a thread pool thread. You have to be very careful in your event handler...
Post a Comment
Read more