Importance of screenshots attached when logging a defect
Screenshots and video recordings: Attaching a screenshot of the defect and its video recording can help you to locate the issue quickly.
Expected vs. actual results: Convey what should be the expected results and what is the actual result to help the developer get a clear picture of what's expected and what's not.
Log Defects
Defect logging is simply finding bugs and defects in the application that is being tested. The testing team checks for potential issues and logs the defects along with their status and priority before assigning it to the development team.
▪ Defect ID - Unique identification number for the defect.
▪ Defect Description - Detailed description of the defect including information about the module in which defect was found.
▪ Version - Version of the application in which defect was found.
▪ Steps - Detailed steps along with screenshots with which the developer can reproduce the defects.
▪ Date Raised - Date when the defect is raised
▪ Reference- where you Provide reference to the documents like . requirements, design, architecture or may be even
screenshots of the error to help understand the defect
▪ Detected By - Name/ID of the tester who raised the defect
▪ Status - Status of the defect , more on this later
▪ Fixed by - Name/ID of the developer who fixed it
▪ Date Closed - Date when the defect is closed
▪ Severity which describes the impact of the defect on the application
▪ Priority which is related to defect fixing urgency. Severity Priority could be High/Medium/Low based on the impact urgency at which the defect should be fixed respectively
STLC
The Software Testing Life Cycle (STLC) is a systematic approach to testing a software application to ensure that it meets the requirements and is free of defects. STLC has different phases.
.
1:Requirement Analysis
Requirement Analysis is the first step of the Software Testing Life Cycle (STLC). In this phase testers understands the requirements like what is to be tested. If anything is missing or not understandable then the testers meets with the stakeholders to better understand the detailed knowledge of requirements.
2:Test Planning.
Test Planning is the most efficient phase of the software testing life cycle where all testing plans are defined. In this phase manager of the testing, team calculates the estimated effort and cost for the testing work. This phase gets started once the requirement-gathering phase is completed.
3:Test Case Development
The test case development phase gets started once the test planning phase is completed. In this phase testing team notes down the detailed test cases. The testing team also prepares the required test data for the testing. When the test cases are prepared then they are reviewed by the testers team.
4. Test Environment Setup
Test environment setup is a vital part of the STLC. Basically, the test environment decides the conditions on which software is tested. This is independent activity and can be started along with test case development. In this process, the testing team is not involved. either the developer or the customer creates the testing environment.
5. Test Execution
After the test case development and test environment setup test execution phase gets started. In this phase testing team starts executing test cases based on prepared test cases in the earlier step.
6. Test Closure
Test closure is the final stage of the Software Testing Life Cycle (STLC) where all testing-related activities are completed and documented. The main objective of the test closure stage is to ensure that all testing-related activities have been completed and that the software is ready for release.
At the end of the test closure stage, the testing team should have a clear understanding of the software’s quality and reliability, and any defects or issues that were identified during testing should have been resolved. The test closure stage also includes documenting the testing process and any lessons learned so that they can be used to improve future testing processes.
Requirement Analysis Phase
SDLC
SDLC is a software development lifecycle. It is a systematic and step by step approach to develop a software. It describes different phases involved in the development process.
1:Requirement Analysis
Collect the requirements from the customer and prepare certain documents. Each and everything will be documented. Business people like project manager, product manager are speak to customer collect the requirements and prepare SRS document, in that document they will mention all the requirements what customers need.
Ex; Opening account in bank, we need name, date of birth, photo, address proof, Identity proof, minimum deposit, customer signature
2:System Design
Based on the documents the designers will prepare the design document. Designers divide the the entire requirement into high level modules and low level modules based on the application.
Ex: We need to sorted out each and every module like login page, Home page, transfer money, saving money.
3:Implementation
Design phase completed the developer will develop the software based on the design document.
Ex: Based on design document they have some input and then they will develop software.
4:Testing
After completion of development the testing phase start, In this phase testers involved and test the software .Testers check the application all the functionality is working or not.
Ex: In the login page ,they will use some input and check the application.
5:Deployment
To install the software in customer environment then start using the software.
Ex: The application fulfill all the requirements and run properly.
6:Maintanance
Any issues in the deployment side are resolved in this phase.
Use case
Describes the system behavior. It explains the functionality or requirement, the customer requirement or project requirement can be specify in the use cases
Use case is a representation of which describes the behavior of system to do a particular task and accomplish the goal. It is a technique that helps to identify test cases and also it is a description of particular use of the system by a user .
Example:
The purpose of a tester in a software development team
After build the product, the testers detects if any bugs in the product in parallel with the development team. Because of the testing , preventing bugs, reducing development and improving performance and finally they give the quality product to customer.
User Acceptance Test User Acceptance Testing (UAT) is one of the last stages of the software development life cycle. It is performed after t...
