Posts

Showing posts with the label Test Cycle

Software Testing Life Cycle

Image
SOFTWARE TESTING LIFE CYCLE: 1) TEST INITIATION: In General, System testing process or STLC starts with test initiation or test commencement. In this phase, project manager or Test Manager selects the reasonable approaches which are followed by Test Engineers. He prepares a document called TEST STRATEGY DOCUMENT in IEEE 829 Format. TEST STRATEGY document is developed for each project. This document defines the scope and general directions or approach or path for testing in the project. TEST STRATEGY MUST ANSWER THE FOLLOWING: 1. When will testing occur? 2. What kind of testing occur? 3. What kinds of risks come? 4. What are the critical success factors? 5. What is the testing objective? 6. What tools will be used? TEST STRATEGY DOCUMENT FEATURES ARE AS FOLLOWS: 1) SCOPE & OBJECTIVE: Brief account & purpose of the project. 2) BUDGET ISSUES: Allocated budget for the project 3) TEST APPROACH: Defines test approach between development stages & testing fa...

Defect Life Cycle or a Bug Lifecycle in Software Testing

Image
What is a Defect Life Cycle or a Bug Lifecycle in software testing? Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing. The bug has different states in the Life Cycle. The Life cycle of the bug can be shown diagrammatically as f ollows: Bug or defect life cycle includes following steps or status: New:  When a defect is logged and posted for the first time. It’s state is given as new. Assigned:  After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer and the developer team. It’s state given as assigned. Open:  At  this state the developer has started analyzing and working on the defect fix. Fixed:  When developer makes necessary code changes and verifies the changes th...

Test Cycle for Requirements based Function Test

Test Cycle for Requirements based Function Test An effective test cycle must have a defined set of processes and deliverables. The primary processes / deliverables for requirements based Function test are: Test Planning, Partitioning / Functional Decomposition, Requirements Definition / Verification, Test Case Design, Traceability (Traceability Matrix), Test Case Execution, Defect Management, and Coverage Analysis. Which processes and deliverables apply to any given testing situation are dependent on available resources (people, source materials, time, etc.) and the mandate of the test organization. Test Planning During planning the Test Lead with assistance from the test team defines the scope, schedule, and deliverables for the function test cycle. The Test Lead delivers a Test Plan (document) and a Test Schedule (work plan) - these often undergo several revisions during the testing cycle. Partitioning - Functional Decomposition Functional decomposition of a system (or ...