In this blog we are discussed different Test Management and Automation tools.
Testing Guideline
• It is based on business requirement, system requirement and user requirement etc.
• It is also depend on system performance, system maintenance, system functionality, system process, input-output value of system etc.
• Testing guideline shows the combination SDLC & STLC.
There are five types of guideline.
1. Testing should uncover software defects and improve software quality.
• Test team should focus on finding the defects in the software like any deviation from the software requirement specification (SRS) or any difference from the desired output.
• Also test team should focus on performance, reliability of software so as to improve software quality.
2. Testing should be done throughout the SDLC.
• Testing is done only after certain phases of development, so test team is not involved
throughout the SDLC.
• This is not the right approach to get the best quality software’s.
• In order to do effective testing the test team should be included from the requirements phase till the implementation phase of the software.
3. Testing should do both black-box and white-box testing
• Test team should perform both black-box testing or functional testing,
– i.e. if the software should produce certain output or input values or expected results .
• Also the white-box testing or structural testing which tests the internal logic of the system should also be done for the software.
4. Testing should be performed by using business logic.
• Any software application performs some business logic and provides the solution.
• The test team should test all the business logic of the software and ensure that the logic is implemented correctly and provides desired results.
5. Testing should be performed effectively and reduce software risks.
• Testing team should put their full effort and perform testing effectively with minimal resources.
• The test process should be well defined so that there is minimal variance between the tasks performed from tester to tester.
• Since software testing is the control which provides management with the risk information so that they can take necessary actions to reduce the project and product risks.
Test Strategy
• A Test Strategy document is a high level document normally developed by project manager.
• This document defines “Testing Approach” to achieve testing objectives.
• The Test Strategy is normally derived from the Business Requirement Specification document (BRS).
• The Test Strategy document is a static document meaning that it is not updated too often.
• for larger projects, there is one Test Strategy document and different number of Test Plans for each phase or level of testing.
• Some companies include the “Test Approach” or “Strategy” inside the Test Plan, which is fine and it is usually the case for small projects.
Different Components of the Test Strategy document
• Scope and objectives
• Business issues
• Roles and responsibilities
• Communication and status reporting
• Test deliverability
• Industry standards to follow
• Test automation and tools
• Testing measurements and metrics
• Risks
• Defect reporting and tracking
• Change and configuration management
• Training plan
Test Planning
• The Test Plan document on the other hand, is derived from the Product Description, Software Requirement Specification(SRS), or Use Case Documents.
• The Test Plan document is usually prepared by the Test Lead or Test Manager.
• the focus of the document is to describe what to test, how to test, when to test and who will do what test.
• It is not uncommon to have one Master Test Plan which is a common document for the test phases and each test phase has their own Test Plan documents.
Test Planning content
• Test Plan id
• Introduction
• Test items
• Features to be tested
• Features not to be tested
• Test techniques
• Testing tasks
• Features pass or fail criteria
• Test environment (Entry criteria, Exit criteria)
• Test deliverables
• Staff and training needs
• Responsibilities
• Schedule
– This is a standard approach to prepare test plan and test strategy documents, but things can vary company-to-company
Test Plan Guidelines
• Make the plan usable.
• Avoid Redundancy.
• Be Specific.
• Make use of list and tables.
• Review a test plan after preparation.
• Update when necessary.
Test Design
• By test design we means to create a test plan for
• how to implement an idea & technique or method or way for performing a task.
• So, Test Design is creating a set of inputs for given software that will provide a set of expected outputs.
There are two main categories of Test Design.
– Static Techniques
– Dynamic Techniques
Static Techniques
• Informal Reviews
• Technical review
• Inspection
• Static Analysis
– Data flow
– Control flow
Dynamic Techniques
• Structure - based
• Experience- based
• Specification - based
Test Execution Cycle
• Different part of the Test execution cycle
– Test Cases
– Test Data
– Test result
– Test Report
Following Process under test execution cycle
– Design Test cases
– Prepare Test data
– Run program with test data
– Compare Result to test cases
Test Status Reporting
• Test status reporting is primarily the responsibility of the test engineers performing the test and it plays a role in the test phase of the software development lifecycle.
• It is important to track defects, project issues, and pending tasks.
• Test status reporting should also occur on a very regular basis (such as weekly)
• It is helpful to be able to compare the testing process to a baseline plan and to weight the quality of the system by the number of defects.
• Effective test status reporting notifies management and other members of the project team
– of test results,
– defects that are found during testing,
– and helps to determine the need for action items.
• When preparing a test status report, it would be useful to include information such as
– the number of test cases and their states,
– the number of defects found and their states,
– patterns and trends observed during testing,
– known risks, schedule changes, etc.
• Test status reports should provide information in terms of features, schedule, budget, and so on.
Sample Test Status Report Template
• Prepared By: Name
• Date of Preparation: Date
• Accomplishments: List of accomplishments such as amount of test cases completed, reduction in defects, etc.
• Issues: List of issues that management and the team should know about.
– Also include items that may affect schedule, budget etc.
• Goal and Priorities: List any pending action items,
– new tasks, goals for any upcoming rounds of testing etc.
• Defect status: List of defects found and their current statuses
Download link for more Detail: Test Management and Automation
Or follow my blog from below link:
https://cdprajapati.blogspot.com/p/blog-page.html
0 Comments