What is severity
and priority of bug? Give some example.
Priority: concern with application from the business point of view.
It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?
Severity: concern with functionality of application. It deals with the impact of the bug on the application.
It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?
Severity: concern with functionality of application. It deals with the impact of the bug on the application.
How much the bug is
affecting the functionality of the application?
Ex.
- High Priority and Low Severity:
Company logo is not properly displayed on their website. - High Priority and High Severity:
Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled." - Low Priority and High Severity:
If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
- There is a mistake like "You have registered success"
instead of successfully, success is written.
What is
difference between Smoke testing and Sanity Testing?
The difference between smoke and sanity
testing is described below:
- Sanity testing is performed when new build is released after fixing
bugs where as smoke testing is performed to check the major
functionalities of the application.
- Sanity is performed by the tester or the developer but smoke
testing can be performed by the tester or developer.
- Smoke testing is performed earlier where as sanity is performed
after the smoke testing.
- Sanity testing is narrow and deep approach of testing and smoke
testing is focused testing based on major functionalities.
What is difference
between Retesting and Regression testing?
The difference between Retesting and
Regression testing are below:
- Retesting is done to verify defects fixes where as regression is
perform to check if the defect fix have not impacted other functionality
that was working fine before doing changes in the code.
- Retesting is planned testing based on the defect fixes listed where
as regression is not be always specific to any defect fix. Also regression
can be executed for some modules or all modules.
- Retesting concern with executing those test cases that are failed
earlier whereas regression concern with executing test cases that was
passed in earlier builds.
- Retesting has higher priority over regression, but in some case
retesting and regression testing are carried out in parallel.
Explain bug
life cycle.
Bug Life Cycle:
- When a tester finds a bug .The bug is assigned with NEW or OPEN
status.
- The bug is assigned to development project manager who will analyze
the bug .He will check whether it is a valid defect. If it is not valid
bug is rejected, now status is REJECTED.
- If not, next the defect is checked whether it is in scope. When bug
is not part of the current release .Such defects are POSTPONED
- Now, Tester checks whether similar defect was raised earlier. If
yes defect is assigned a status DUPLICATE
- When bug is assigned to developer. During this stage bug is
assigned a status IN-PROGRESS
- Once code is fixed. Defect is assigned with FIXED status.
- Next the tester will re-test the code. In case the test case passes
the defect is CLOSED
- If the test case fails again the bug is RE-OPENED and assigned to
the developer. That’s all to Bug Life Cycle.
What is alpha and
beta testing?
Alpha testing: is performed by the IN-House developers. After alpha testing the
software is handed over to software QA team, for additional testing in an
environment that is similar to the client environment.
Beta testing: It is performed by end user. So that they can make sure that the
product is bug free or working as per the requirement. IN-house developers and
software QA team perform alpha testing. The public, a few select prospective
customers or the general public performs beta testing.
What are test
driver and test stub and why we need them?
- The Stub is called from the software component to be tested. It is
used in top down approach.
- The driver calls a component to be tested. It is used in bottom up
approach.
- Both test stub and test driver are dummy software components.
We need test stub and test driver
because of following reason:
- Suppose we want to test the interface between modules A and B and
we have developed only module A. So we cannot test module A but if a dummy
module is prepare, using that we can test module A.
- Now module B cannot send or receive data from module A directly so,
in these cases we have to transfer data from one module to another module
by some external features. This external feature used is called Driver.
What is difference between QA, QC and Software Testing?
Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.
Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.
Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.
Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.
Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.
What are verification and validation and difference between these two?
Verification: process of evaluating steps which is followed up to development phase to determine whether they meet the specified requirements for that stage.
Validation: process of evaluating product during or at the end of the development process to determine whether product meets specified requirements.
Validation: process of evaluating product during or at the end of the development process to determine whether product meets specified requirements.
Difference between Verification and Validation:
- Verification is Static Testing where as Validations is Dynamic Testing.
- Verification takes place before validation.
- Verification evaluates plans, documents, requirements and specifications, where as Validation evaluates product.
- Verification inputs are checklist, issues list, walkthroughs and inspection, where as in Validation testing of actual product.
- Verification output is set of documents, plans, specifications and requirement documents where as in Validation actual product is output.
Test Design Techniques
1) Boundary value analysis: is software testing technique in which test cases are designed to
include representatives of boundary values in and out of a given range.
Example:When ever the engineers need to develop test cases for a range kind of input then they will go for boundary value analysis .Which describes to concentrate on the boundary of the range.
LB-1 LB LB+1 MV UB-1 UB+1
2) Equivalence partitioning: also, called Equivalence Class Partitioning is a software testing technique that divides the given condition into partitions and one input data from each partition can be chosen for testing.
Example:When the test engineers need to develop test cases for a feature which has more number of validation then one will go for equableness class partition.Which describe first divide the class of inputs and then prepare the test cases.
Develop the test cases for Email test Box whose validations are as follows.
Requirements:
1. It should accept Minimum 4 characters maximum 20 characters.
2. it Should accept only small character.
3. It should accept @ and _ special symbols only.
Boundary Value Analysis:
LB-1 LB LB+1 MV UB-1 UB UB+1
3ch 4ch 5ch 12ch 19ch 20ch 21ch
Equavlance Class :
valid Invalid
4char 3char
5char 21char
12char A-Z
19char 0-9
20 char All the special character apart from @ and _
a-z Alpha numeric
@ Blank space
_ dismal number
3) State transition testing: is a black box testing technique, which can be used to design test cases for a system that acquires finite number of states and can transit from one state to another upon specific events.
4) Error Guessing: is a technique where experience of a tester is used to find the errors or part of application with highest possibility of finding errors. This is skill-based technique without any rules.
5) Use case testing: In this technique, use cases/scenarios are used to write the test cases. Interaction of users and system is described in a use case.
Some more test design techniques:
6) Statement coverage
7) Condition Coverage
8) Exploratory testing
9) Decision Table : Use for logical coverage and we uses data flow diagram.
Example:When ever the engineers need to develop test cases for a range kind of input then they will go for boundary value analysis .Which describes to concentrate on the boundary of the range.
LB-1 LB LB+1 MV UB-1 UB+1
2) Equivalence partitioning: also, called Equivalence Class Partitioning is a software testing technique that divides the given condition into partitions and one input data from each partition can be chosen for testing.
Example:When the test engineers need to develop test cases for a feature which has more number of validation then one will go for equableness class partition.Which describe first divide the class of inputs and then prepare the test cases.
Develop the test cases for Email test Box whose validations are as follows.
Requirements:
1. It should accept Minimum 4 characters maximum 20 characters.
2. it Should accept only small character.
3. It should accept @ and _ special symbols only.
Boundary Value Analysis:
LB-1 LB LB+1 MV UB-1 UB UB+1
3ch 4ch 5ch 12ch 19ch 20ch 21ch
Equavlance Class :
valid Invalid
4char 3char
5char 21char
12char A-Z
19char 0-9
20 char All the special character apart from @ and _
a-z Alpha numeric
@ Blank space
_ dismal number
3) State transition testing: is a black box testing technique, which can be used to design test cases for a system that acquires finite number of states and can transit from one state to another upon specific events.
4) Error Guessing: is a technique where experience of a tester is used to find the errors or part of application with highest possibility of finding errors. This is skill-based technique without any rules.
5) Use case testing: In this technique, use cases/scenarios are used to write the test cases. Interaction of users and system is described in a use case.
Some more test design techniques:
6) Statement coverage
7) Condition Coverage
8) Exploratory testing
9) Decision Table : Use for logical coverage and we uses data flow diagram.
No comments:
Post a Comment