Software Testing Life Cycle

Manual Testing

Manual testing plays a vital role in finding defects. Testers play the role of an end user, and use most of all features of the application to ensure correct behavior. For the completeness of testing, the tester follows a written test plan that leads through a set of test cases. Defect tracking tool are- Bugzilla, JIRA and Test Track Pro.  Etc…

STLC (Software Test Life Cycle)

Software Testing Life Cycle or STLC is a comprehensive group of testing related steps followed to deliver quality product. Testing has become an important phenomenon during and after development of any software project. The various steps in testing process are:

STLC

• Test planning

This is the initial and key step in software testing. This step determines the overall flow of testing process starting from:

• Requirement gathering, its analysis and specifications
• Framing the test plan and test scenario
• Preparing test cases and its approval
• Tools selection and confirmation

We carry out our test planning on the basis of IEEE Standard for Software Test Documentation and other industry specifications.

• Testing environment and harness preparation

This stage is defined by test automation framework design and development and test scripts creation. SCMS has state-of-the-art testing equipment, system software, and web middleware. This ensures creation of proper testing environment. It also helps in essentially decreasing the time for testing configurations deployment.

• Test execution

The manual and automated software testing, as specified in the test plan, is applied in a dynamic state of code. The approaches and methods are utilized to validate the executable code developed meeting the specifications stated at start of software project.

For each of these types of testing we have established approaches, proven testing tools, and adjusted reporting documents templates. Testing techniques applied:

• Black Box / White Box testing
• Ad Hoc / Exploratory testing
• Scripted testing

• Test Reporting

We use the industry-recognized bug tracking tools like Jira, BugZilla. The test reports are well-documented and the spotted bugs are reported to the developer after the testing is completed.

• Final reporting and analysis

This is final step of test cycle. It involves the final report preparation and project metrics generation. The defects spotted are analyzed and recommendations are made for improvements.

Below is another way of defining STLC

Test Requirements 

? Requirement Specification documents
? Functional Specification documents 
? Design Specification documents (use cases, etc) 
? Use case Documents 
? Test Trace-ability Matrix for identifying Test Coverage

Test Planning

? Test Scope, Test Environment
? Different Test phase and Test Methodologies
? Manual and Automation Testing
? Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc
? Evaluation & identification ? Test, Defect tracking tools

Test Environment Setup

? Test Bed installation and configuration
? Network connectivity?s
? All the Software/ tools Installation and configuration
? Coordination with Vendors and others

Test Design
? Test Traceability Matrix and Test coverage
? Test Scenarios Identification & Test Case preparation
? Test data and Test scripts preparation
? Test case reviews and Approval
? Base lining under Configuration Management

Test Automation

? Automation requirement identification
? Tool Evaluation and Identification.
? Designing or identifying Framework and scripting
? Script Integration, Review and Approval
? Base lining under Configuration Management

Test Execution and 
Defect Tracking

? Executing Test cases
? Testing Test Scripts
? Capture, review and analyze Test Results
? Raised the defects and tracking for its closure

Test Reports 
and Acceptance

? Test summary reports
? Test Metrics and process Improvements made
? Build release
? Receiving acceptance

Hope this will help for all