A. Evolution
♦ 1960's trends:
♦ 1990's trends:
♦ 2000's trends:
Trends and test capabilities are changing. Now requires testers to pay more attention to technology and processes. Now the test is not limited to errors are found, and a wider range, from the outset of the project need not even finalized. Because the test is standardized. Like the software development life cycle, as tests also have a life cycle. In subsequent chapters, I will discuss the life cycle is and what does it relate to software testing, and will attempt to detail.
let's start!
II. What is the life cycle?
In simple terms the life cycle is the order changes from one form to another form.
These changes may occur on any tangible or intangible things.
Each entity from start to retired / extinction has a life cycle.
In a similar manner, also a software entity.
Like software development involves a series of steps as a test, there are some steps you should take in a certain order.
This test is performed activities in a systematic and planned manner phenomenon known as life-cycle test.
III. What is software testing life cycle (STLC)
Testing life cycle means a test procedure, which has certain steps to determine the order of execution, in order to ensure that the quality objectives.
In STLC process, each activity carried out in a planned and systematic way.
Each stage has different objectives and deliverables.
Different organizations have different stages in STLC in; but the fundamentals remain the same.
The following are the various stages of STLC:
- Requirements phase
- Planning stages
- Analysis phase
- design phase
- Implementation phase
- The implementation phase
- Conclusion phase
- Closure phase
# 1 requirements phase:
At this stage STLC, analysis and research requirements. Brainstorming meetings with other teams and try to determine whether these requirements can be tested. This stage helps determine the test range. If the feature is not available in any test, please communicate at this stage, so that you can plan mitigation strategies.
# 2 planning stage:
In practice, the test plan is the first step in the testing process. At this stage, we determined that contribute to achieving the goal of testing activities and resources. During planning, we also try to identify indicators, collection and tracking of these indicators.
Plan on what basis? Only requirement?
The answer is no. Indeed constitutes one of the basic requirements, but there are two other very important factor affecting the test plan. these are:
- organize the testing strategy.
- Risk analysis / risk management and prevention.
# 3 analysis phases:
STLC stage is defined to be tested "WHAT". Our basic condition is determined by test requirements documents, product risk and other test basis. The test conditions should be traced back to requirements. Factors affecting the test conditions identified are many:
- the level and depth of testing
- the complexity of the product
- product and project risk
- involving software development life cycle.
- Test management
skills and knowledge of a team -
- Availability stakeholders.
We should try to write in a detailed manner the test conditions. For example, for e-commerce Web application, you can set test conditions "Users should be able to make a payment." Or you can say "Users should be able to NEFT, debit and credit card payment" is explained in detail. The most important advantage to write detailed test conditions is that it increases the test coverage, because the test case will be prepared in accordance with the test conditions, these details will trigger a more detailed written test, will eventually increase the coverage. Also make sure to exit the standard test, which is determined to stop some of the conditions tested.
# 4 design stage:
This phase defines "HOW" for testing. This phase involves the following tasks:
- detailed description of the test conditions. The test conditions are sub-divided into a plurality of conditions to increase the coverage.
- identify and acquire test data
- identifying and setting up a test environment.
- Create requirements traceability Metrics
- Create test coverage metrics.
# 5 implementation phases:
The main task of STLC stage is to create detailed test cases. To determine the priority of test cases, test cases can also determine which will become part of the regression suite. Before finalizing the test case, it is important to be reviewed to ensure the accuracy of test cases. In addition, before the actual execution begins, do not forget to cancel the test signature. If your project involves automation, make sure the candidates for automation of test cases and test cases continue to write the script. Do not forget to view them!
# 6 implementation phase:
As the name suggests, this is software testing life cycle stage of practical implementation. But before you begin, make sure that your input conditions. Implementation of test cases, defects recording of any discrepancies. Also complete traceability of indicators to track your progress.
# 7 Conclusion stage:
The STLC phase focused on exit criteria and reporting. According to choose your projects and stakeholders, you can decide whether you want to send a weekly report report / daily reports. You can send different types of reports (DSR - Daily status reports, WSR - weekly status report) but it is important that the contents of the report vary, depending on which report you send. If the project manager belongs to test the background, so they are more interested in the technical aspects of the project, so please include the technical content (by the number of test cases, failure, caused by the defect, the severity of a defect, etc.) in the report. However, if you are, they may not be interested in the technical issues reported to the upper stakeholders, so please report them to pass the test to reduce the risk of.
# 8 closing phase:
Close the active tasks include the following:
- Check the test is complete. Are all test cases are executed or missing. Check that no open defect severity 1.
- take the lessons learned lessons learned meeting and create files. (Including what goes well, what has improved and what aspects could be improved)
Four Summary:
Let's try to summarize software testing life cycle (STLC) it!
| S.No | Stage name | Entry Standard | Implementation of activities | Deliver |
|---|---|---|---|---|
| 1 | demand | Requirements Specification document application design document user acceptance criteria file |
Demand for brainstorming. Create a list of requirements and clarify your doubts. . Understand the feasibility of whether demand can be tested if your project requires automation, please automation feasibility study |
RUD (needs to understand the document. Test the feasibility report of automation feasibility report |
| 2 | plan | Updated requirements document. Test the feasibility report " Automation feasibility report |
定义项目的范围 进行风险分析并制定风险缓解计划。 执行测试评估 确定整体测试策略和流程。 确定工具和资源，并检查是否有任何培训需求. 识别环境 |
测试计划文档. 风险预防文件 测试评估文件 |
| 3 | 分析 | 更新的需求文档 测试计划文档 风险文档 测试评估文档 |
确定详细的测试条件 | 测试概要文件。 |
| 4 | 设计 | 更新的需求文档 测试概要文件 |
详细说明测试条件。 识别测试数据 创建可跟踪性指标 |
详细的测试条件文件 需求可追溯性指标 测试覆盖指标 |
| 5 | 实施 | 详细的测试条件文件 | 创建并查看测试用例。 创建并查看自动化脚本。 确定回归和自动化的候选测试用例. 识别/创建测试数据 签下测试用例和脚本。. |
测试用例 测试数据 测试脚本 |
| 6 | 执行 | 测试用例 测试脚本 |
执行测试用例 记录 bugs / 出现差异的缺陷 报告状态 |
测试执行报告 缺陷报告 测试日志，缺陷日志 更新需求可跟踪性指标 |
| 7 | 结论 | 更新了包含结果的测试用例 测试关闭条件 |
提供准确的数字和测试结果 确定减轻的风险 |
更新了可追溯性指标 测试总结报告 更新风险管理报告 |
| 8 | 关闭 | 测试闭合条件 测试总结报告 |
进行回顾性研究并了解所学到的经验教训 | 经验教训文件 测试矩阵 测试结束报告. |
HAPPY TESTING!!