Tuesday, 2 December 2014
Software Testing Process
Software Testing Process
 |
| Software Testing Process |
Integrating SDLC and Software Testing Process:
 |
| Integrating SDLC and Software Testing Process |
- When SRS is baselined , project management recruit programmers and testers into current project.
- Project or product planning prepared by PM is more detailed. But testing team prepare separate test planning as well.
- Testing team start writing test cases (In order to start writing test cases testing team study the SRS)and after that they detect the defects after getting the build from the development team.
Test Initiation or Commencement
Test Initiation or Commencement
Software testing process starts when SRS is baselined. In software
testing process, test initiation is the first stage. In this stage
project manager or test manager category people prepare test strategy or
test methodology document which specifies an approach to be followed by
the testing team. There are three types of strategy in testing:
- Exhaustive Testing
- Planned Testing
- Ad-hoc Testing
From software testing principle, exhaustive testing is impossible. Due
to this reason, test management concentrate on planned testing or ad-hoc
testing methodologies. Ad-hoc testing is followable when testing team
have some risks. When there are no risks testing team favors planned
testing/ Formal testing/Optimal testing. From this planned testing,
project manager or test manager prepare a test strategy document like
below:
- Scope and Objective
- Business Issues
- Test Responsibilities in Matrix
- Roles and Responsibilities
- Status of Communication
- Test Automation and Testing tools
- Defect Reporting and Tracking
- Test Measurement and Matrix
- Test Management
- Risks and Assumptions
- Training Plan
Scope and Objective- In this importance of the current project is described
Business Issues- In this budget allocated for the testing project is mentioned like below:
Business Issues- In this budget allocated for the testing project is mentioned like below:
 |
| Budget Allocation |
 |
| Test Responsibilities in Matrix |
Roles and Responsibilities- It consists of the jobs in the testing team and each job requirements like below:
 |
| Roles and Responsibilities |
Status and Communication- In every two jobs in testing team are co-ordinated via different channels. For example Personal Meetings, Offline Meetings, Online Chatting, Video Conferencing and internal communicator etc.
Test Automation and Testing Tools- In this need for test automation in current project and available testing tools in the company is mentioned.
Defect Reporting and Tracking- In this required negotiation channels in between developers and testers while reporting and tracking of defects is mentioned.
Test Measurement and Metric- Measurement is a basic unit and Metric is a compound unit. In order to estimate the testing process status, testers use a set of measurement and metric.
Test Management- Testing team need a sharable location to store all testing deliverables for future called as test base.
 |
| Test Management |
Risks and Assumptions- In this List of all risks (which might come in future) and assumptions (to overcome those risks) is mentioned.
Training Plan- Testing team need training on the customer requirements in current project. In this training, testers are trained by BA,SA and SME
Training is optional to the testers if the testers have experience in the current project. The domain of the current project may be Banking, Insurance, Finance, Sales, Telecommunications, Health Care, eCommerce, e-learning etc.
Test Planning
Test Planning
After completion of the test strategy preparation, PM (Project Manager) can sign in a Test Lead. The test lead can study the test strategy document and can start preparation of the test plan document.
 |
| Test Plan |
(a) Team Formation- Test lead can start test planning process with testing team formation. While formation of the team, test lead depends on the below factors:
- Project Size (Number of Functionalities)
- Test Duration (Number of Working Days)
- Available Testers on bench
- Available resources in test environment
Case Study
 |
| Team Formation |
(b) Identifying Tactical Risks- After completion of testing team formation ,test lead concentrates on risk identification which includes-
- Lack of Domain Knowledge to Testers
- Lack of Documentation
- Lack of Time
- Lack of Resources
- Delays is Delivery
- Lack of developer's seriousness
- Lack of Communication
(c) Preparation of Test Plan- After completion of testing team
formation and risk analysis, test lead starts preparation of test plan
document in IEEE (Institute of Electrical and Electronics Engineering)
829 format.
Click here to know about the 'Test Plan Format'
(d) Review Test Plan- After completion of test plan document preparation test lead conducts a review meeting along with project manager, business analyst, system analyst and selected testers for the current project. In this review meeting test lead performs the test changes in the test plan if needed (it depends upon the feedback)
(d) Review Test Plan- After completion of test plan document preparation test lead conducts a review meeting along with project manager, business analyst, system analyst and selected testers for the current project. In this review meeting test lead performs the test changes in the test plan if needed (it depends upon the feedback)
Test Plan Format
Test Plan Format
1)Test Plan ID- It is a unique number or name for future reference.
(2)Introduction- It has description about the current project.
(3)Features or Modules- It has list of modules in the current project.
(4)Features to be tested- It has the number of modules which are to be tested in the current project.
(5)Features not to be tested-It has the number of modules which are not to be tested in the current project.
(6) Test Approach/Strategy- It is generally just an attachment provided by the Project Manager.
(7)Test Environment- It consists of the required hardware and software for testing of the current project.
(8)Entry Criteria- These are the criterias in order to start the test execution which includes:
- Test cases is prepared and reviewed
- Test environment is established
- Software under test has come from the developers
- Show stopper in SUT (Or Deadlock)
- Test Environment abandoned
- More defects in pending (Quality Gap)
- All Modules Tested
- Time exceeded
- All Major Defects closed
(11)Test Deliverables- These are the list of documents to be prepared by testers in testing. For example:
- Test Scenarios
- Test cases
- Automation Programs
- Test Logs
- Defect Reports
- Status Reports
(13)Responsibilities- This includes the work allocation to the
selected testers in terms of modules or testing topics. It just
represent 'Who to Test'.
(14)Schedule- It includes the Date and Time for the testing. It represents 'When to test'
(15)Risks and Assumptions- It consists of the lists of previously analysed risks and solutions to overcome them.
(16)Approvals- It includes the signature of the test lead and the project manager.
Monday, 1 December 2014
Vijay was born in Chennai to a film producer and director S. A. Chandrasekhar and Shoba Chandrasekhar, a playback singer. He had a sister named Vidhya Chandrasekhar who died at the age of two. Vijay went on to do Visual Communications at Loyola College, Chennai.
Vijay married Sangeetha Sornalingam of Sri Lankan Tamil descent on 25 August 1999.[32] They have two children, a son Sanjay born in 2000 in London,[33] and a daughter Divya born in 2005 in Chennai. His son's name was a combination of the names Sangeetha and Vijay in which the first three letters of Sangeetha was taken and the last three letters of Vijay was taken. Also, his daughter's name Divya is derived from the name of his late sister, Vidya.
His cousin Vikranth is an actor. His uncle S. N. Surender is a playback singer and dubbing artist.
Subscribe to:
Posts (Atom)