40)What is Test strategy?
-Test strategy describe the testing phrase in SDLC.
-It is a the high level plan for how you are going to approach testing.
-A test strategy addresses: How, where, who and when
How: types of testing needs to follow (manual or automated)
where: test environment details
who: testing resources
when: timing
-It is make sure that the effort , timelines and cost are all within acceptable limits.
41)How many levels are there in Test strategy?
Test strategy has different levels
1)organization level
2)Application level or product level
3)project level
42)Test Strategy Essentials?
-Define the objectives, approach and timelines for the testing effort.
-Identify test activities and define roles and responsibilities
-Define test environment and data requirements
-Inform the test approach to stake holders
43)What is Test Plan?
Test plan describes the more specific to the testing phase like Unit Testing, Integration Testing, System Testing.
45)What is Test Scenario?
-Test scenario is an user action.
-Test scenario outline the functionality to be tested with specifying steps to be followed to test functionality mentioned in usecase /functional specification.
-Test scenarios created before starting of development.
-Test scenario document prepared from Business Requirement / Functional specification Document /High level design Document or Usecase Document/Test Plan
-One requirement mapped more than one Test Scenario
46)Types of Test Scenarios?
Two types of test scenarios
1)Positive scenarios
2)Negative scenarios
Positive scenarios:
-Test with valid input
-This also called as Happy flow
-Example sum of two digits with two numbers
Negative scenarios:
-Test with invalid input
-Example sum of two digits with one number , another with character type data
47)What is Test Case?
-Test Case guarantee that all the functionalities covered or not.
-Test Case contains the detailed steps that needs to follow while testing.
-Determine the product or software met client requirements or not
-Help managers to go/no-go (ship/no-ship)
-One Test Scenario mapped more than one test case
48)What is Requirement Traceability?
-Its used to tracing links between client requirements and the deliverables in SDLC
-It is make sure requirements met the requirements
-It is identify which deliverable implement which requirement.
-Identify which deliverables not captured due to not documented.
49)What is an error?
A human action that leads to incorrect result as output
50)What is a Defect?
-An incorrect or incomplete implementation of the functionality mentioned in requirement specification document.
-Not implemented the functionality which is mentioned in FS
-Defects may found in any phrase of SDLC.
51)What is defect classification in testing?
Defects classification done based two factors
1)Defect Severity
2)Defect Priority
52)What is Defect Severity in Testing?
Severity is nothing but impact of the defect on the software and it is classified as below
- Critical
- Major
- Minor
- Cosmetic
53)What is Defect Priority in Testing?
Priority is nothing but importance and order of which defect needs to fix and which is later and it is classified as below
- Urgent
- High
- Medium
- Low
54)Defect life cycle in Testing?
Defect life may have slight difference company to company
Defect gone through the following states
Open: when first the defect is logged
Assigned: when Assign defetct to the respective developer
Resolved: when the developer fixed the defect
(
Resolvedreadyforinspection: when developer fixed the issue , Ready to inspect code chenges by Managers.
Resolvedreadyfortest : after inspecting the developer submitted changes , Manager move the defect to test.
)
Re-Open: when the defect is still exist.
Closed: when the defect is tested and felt it is fixed.
Rejected: when the defect is not valid.
55)What is Test Metrics , Why Need this metric?
-Test Metrics used understand the project maturity or status.
-Used to estimate efficiency
-Improve quality
-Improve resource efficiency
-Based on metrics sometimes project plan will be done
Following are some of the test metrices:
Effort Variance:
Formula: [Actual Effort – Planned Effort] / [Planned Effort] * 100
Measured in : %
Schedule Variance:
Formula : [Actual Duration - Planned Duration] /[Planned Duration] * 100
Measured in : %
Testing Defect Rejection Rate:
Formula : [No. of Testing Defects Rejected by the Development Team] / [No. of Testing Defects Raised by the Testing Team] * 100
Measured in : %
Review Efficiency:
Formula: [No. of Peer Review Defects reported ] / [[No. of Review Defects Reported by SQA] + [No. of Review Defects Reported by Peer]] * 100
Measured in : %
Cost Of Quality:
Formula : [[Prevention Effort] + [Appraisal Effort] +[Correction Effort]] / [Total Testing Effort] *100
Measured in : %
Test Development Productivity:
Formula: [Number of Test Cases/scripts created ]/ Actual Effort of creation
Measured in : Ratio
Test Execution Productivity:
Formula: [Number of Test Cases executed] / Actual Effort of Testing
Measured in : Ratio
Testing Defect Density:
Formula: [No. of Testing Defects Reported by testing team] /[No. of Test Cases Executed]
Measured in : Ratio
56)What is Software reliability in Testing?
-Reliability is one of the biggest consider to release the software
-Important reliability figures are below
MTTR-Mean time to repair
MTBF-Mean time between failures
MTTF-Mean time to fail
MTTD-Mean time to detect
Formula's are below:
MTTR = total time spent on repairing/no of repairs;
MTTF= total lifespan across devices/no of failures;
MTTD = total time between failure and detection / no of failures;
57)What is Performance testing?
-Performance testing is not a functional testing so need to test al the functionalities of an application. only test critical functionalities
-To decide response time of various important scenarios in an application / product
-To decide the ideal system configuration
-To decide concurrent users the system will support
58) Types of Performance testing?
-Stress Testing
-Contention Testing
-Volume Testing
-Benchmark Testing
-Load Testing
59)What is Stress Testing?
-To test the server's behavior under unusual, unexpected or extreame conditions.
This test is for:
-When resources are accessed by high number of users
-Application behavior on high loads
-Repeating some conditions or inputs
-Large inputs Etc..
60)What is Contention Testing?
-To test the server behavior if multiple users trying to access same users.
61)What is Volume Testing?
-To test the server behavior by giving large amount of data.
62)What is Benchmark Testing?
– To test the performance or compare of a new server to a known existing software or measurements.
63)What is Load Testing?
–To test the server's performance behavior by giving different workloads, observe system's response time degrades or fails.
For Part1 click here
Thanks for visiting this blog. How is the content?. Your comment is great gift to my work. Cheers.
No comments:
Post a Comment