Software Test Life Cycle (STLC)

-

Definition: It is a sequence of activities conducted during the testing process to ensure software quality goals are met.





PHASE

ENTRY CRITERIA

ACTIVITY

EXIT CRITERIA

DELIVERABLES

Requirement analysis

1. Story is defined properly.

2. Acceptance criteria is clearly mentioned.

1. QA interacts with stakeholders to understand the requirements in detail.

2. Identify the type of testing that will be required(Functional or non-functional)

3. Identify test environment details.

4. Prepare RTM

5. Identify automation feasibility.

1. RTM is ready

2. Automation Feasibility report is done.

1. RTM

2. Automation feasibility report.

Test Planning: The senior QA Manager determines the test strategy, efforts & estimations for the project. Resources, test envmt and testing schedule is also determined. Test plan is prepared and finalized in this phase.

1. RTM

2. Test automation feasibility report.

1. Prepare test plan/strategy doc.

2. Test tool selection

3. Test effort estimation

4. Resource planning and defining roles & responsibilities.

5. Training requirement.

Test plan is approved.(By Product owner)

1. Test plan/Strategy document.

Test Design

1. RTM

2. Automation feasibility report.

3. Test plan

1. Test data is created.

2. Identify and create test case document.

1. Test cases are reviewed & signed off

2. Test data is reviewed & signed-off

1. Test data

2. Test case document.

Test Environment setup

1. System design and architecture docs are available.

2. Environment setup plan is available.

1. Understand and list down the Hardware & Software requirements.

2. Setup environment and Test data.

3. Perform smoke test on the build

1. Environment is ready with Test data.

2. Smoke tests are done & successful.

1. Test environment with test data.

2. Smoke test results.

Test execution

1. RTM, Test plan, Test cases, Test environment, Test data is ready.

2. Unit testing is done.

1. Execute tests as per plan.

2. Document test results and log defects.

3. Map defects to test cases in RTM.

4. Retest defect fixes.

1. All planned tests are executed.

2. Defects are logged and closed.

1. Test cases updated with results.

2. RTM updated with execution status.

3. Defect reports.

Test cycle closure

1. Testing has been completed.

2. Test results are available.

3. Defect logs are available

1. Evaluate cycle completion criteria based on – Time, Test Coverage, Cost, Software Quality, Critical Business Objectives


2. Testing team members meet, discuss and analyze testing artifacts to identify strategies that have to be implemented in future, taking lessons from current test cycle. The idea is to remove process bottlenecks for future test cycles.


3. Prepare Test closure report


4. Document the learning out of the project

Test Closure report signed off by Client.

1. Test closure report.



Comments

Post a Comment

Popular posts from this blog

Jenkins CICD in One Page

-
Image
   Jenkins Architecture: Jenkins follows a Master/Slave architecture where master and slave communicate over TCP/IP protocol Jenkins Architecture has 2 main components: 1. Jenkins Master/Server          2. Jenkins Slave/Node/Build Server 1. Jenkins Master: The Main Server of Jenkins i.e. the brains is the Jenkins Master It is a dashboard which is powered from a war file Runs on port 8080 by default With the help of the dashboard we can configure the jobs/projects but the build takes places in the Node/Slave server By default one node is configured and running in Jenkins Server We can add more nodes using IP addresses, username, passwords using jnlp, ssh or webstart methods The main job of server is: Scheduling build jobs Dispatching builds to the nodes/slaves for actual execution Monitoring the nodes/slaves Recording and Presenting the build results A Master/Server instance of Jenkins can execute build jobs as well i.e. it can also act as a node itself 2. Jenkins Slave: The Jenkins sla
Read more

Why do we need a build tool?

-
Image
Why we need build tool? Consider this scenario where you want to run a java application   You can use java compiler (javac) provided by JDK to compile java code into Byte Code which can then run on any Machine To compile Java Programs using javac you will have to list all java source files to run the entire application Ex., "javac Program1.java Program2.java Program3.java Program4.java" This is a very tedious job. Doing this manually is a pain since there are hundreds of libraries used even in the simplest of Java Application Also one has to add Compilation classpath to make the code work. For example if the code uses libraries like testNG, Selenium etc. You need to add it to Compilation Classpath using following code: "javac -cp testNG.jar; webdriver.jar; lib3.jar" MyProgram.java In conclusion, Compiling java code manually becomes very tedious and complex task Enter Third party build tools like Spring boot, apache-comm
Read more

Deutsche Bank Interview Questions - 2024

-
  - Write a code Read a JSON file in java and get all objects/array objects from it. - How is Vector different than a List? - Collections vs Collection? - How do you make sure a List is not accessed concurrently? - Are Thread.sleep() and wait method from selenium static? - Can we overload sleep() and wait() methods? - Difference between sleep() and wait() methods - What is Transient in Java? - Explain the whole hierarchy of Collections interface - Is ArrayList thread safe? - How to make a list thread safe? - What is Autoboxing and Unboxing in java? - Wrapper classes in java? - Can we have method implementation inside an Interface? - What is Fail fast in java? - Write a program  Find all pairs of elements in an array whose sum is equal to given number array- {4,5,7,11,9,13,8,12,10,10} given number -20. Eg., O/p: should be: 11,9 8,12, 13,7 10,10 - What is fail fast mechanism in Java - Do you know lambda expressions?
Read more