Q1. 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.
Q2. When to start QA in a project?
A good time to start the QA is from the beginning of the project startup. This will lead to plan the process which will make sure that product coming out meets the customer quality expectation. QA also plays a major role in the communication between teams. It gives time to step up the testing environment. The testing phase starts after the test plans are written, reviewed and approved.
Q3. 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.
Q4. 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.
Q5. What is destructive testing, and what are its benefits?
Destructive testing includes methods where material is broken down to evaluate the mechanical properties, such as strength, toughness and hardness.
For example, finding the quality of a weld is good enough to withstand extreme pressure and also to verify the properties of a material.
Benefits of Destructive Testing (DT)
- Verifies properties of a material
- Determines quality of welds
- Helps you to reduce failures, accidents and costs
- Ensures compliance with regulations
Q6. What is Testware?
The testware is:
- The subset of software which helps in performing the testing of application.
- Testware are required to plan, design, and execute tests. It contains documents, scripts, inputs, expected results, set-up and additional software or utilities used in testing.
- Testware is term given to combination of all utilities and application software that required for testing a software package.
Testware is special because it has:
1. Different purpose
2. Different metrics for quality and
3. Different users
2. Different metrics for quality and
3. Different users
Q7. 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.
Q8. 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.
Q9. 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. - Low Priority and Low Severity:
There is a mistake like "You have registered success" instead of successfully, success is written.
Q10. What are the common problems with software automation?
Software problem are listed below:
1. Purchasing the license of tool (QTP, selenium, QC, LR)
2. Lack of skilled Tester to run the tool
3. Expectation that automated tests will find a lot of new defects
4. Maintenance of automated tests
5. Technical problems of tools
2. Lack of skilled Tester to run the tool
3. Expectation that automated tests will find a lot of new defects
4. Maintenance of automated tests
5. Technical problems of tools
Q11. What is the role of QA in a project development?
QA stands for QUALITY ASSURANCE. QA team assures the quality by monitor the whole development process. QA tracks the outcomes and adjusting process to meet the expectation.
The role of Quality Assurance is discussed below:
- QA team is responsible for monitoring the process to be carried out for development.
- Responsibilities of QA team are planning testing execution process.
- QA Lead creates the time tables and agrees on a Quality Assurance plan for the product.
- QA team communicated QA process to the team members.
- QA team ensures traceability of test cases to requirements.
Q13. What is the difference between build and release?
BUILD: is a number given to installable software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.
RELEASE: is a number given to installable software that is handed over to customer by the developer or tester.
The information of build, release and version are displayed in software help page. Using this build and release customer can let the customer team know which release version build thet are using.
The information of build, release and version are displayed in software help page. Using this build and release customer can let the customer team know which release version build thet are using.
eg "9.4.123.2" (Release Number.Version Number.Build Number.Patch Number)
Q14. What are the key challenges of software testing?
Following are some challenges of software testing
1. Application should be stable enough to be tested.
2. Testing always under time constraint
3. Understanding requirements, Domain knowledge and business user perspective understanding
4. Which tests to execute first?
5. Testing the Complete Application
6. Regression testing
7. Lack of skilled testers.
8. Changing requirements
9. Lack of resources, tools and training
2. Testing always under time constraint
3. Understanding requirements, Domain knowledge and business user perspective understanding
4. Which tests to execute first?
5. Testing the Complete Application
6. Regression testing
7. Lack of skilled testers.
8. Changing requirements
9. Lack of resources, tools and training
Q15.Why you choose automated testing over manual testing?
The reasons for choosing automation testing over manual testing are following:
1. Frequency of use of test case
2. Time Comparison (automated script run much faster than manual execution.)
3. Reusability of Automation Script
4. Adaptability of test case for automation.
5. Exploitation of automation tool.
2. Time Comparison (automated script run much faster than manual execution.)
3. Reusability of Automation Script
4. Adaptability of test case for automation.
5. Exploitation of automation tool.
Q16. What is the basis for choosing the SDLC model for development of software?
The choice of SDLC depends on the various factors, how stable are the requirements:
- When the requirements are very clearly know, documented and not subject to change then we can follow the waterfall model.
- Most of the companies follow the V mode for the development because this model includes both verification and validation activities and testing is involved in earlier phase.
- Iterative model can be used to build application where requirement changes after a period of times or application features or added on with smaller release. When the client is ready for the delivery of the product in parts or phases.
Q17. Explain bug leakage and bug release.
Bug Leakage: When customer or end user discovered a bug which can be detected by the testing team. Or when a bug is detected which can be detected in pervious build then this is called as Bug Leakage.
Bug release: is when a build is handed to testing team with knowing that defect is present in the release. The priority and severity of bug is low. It is done when customer want the application on the time. Customer can tolerate the bug in the released then the delay in getting the application and the cost involved in removing that bug. These bugs are mentioned in the Release Notes handed to client for the future improvement chances.
Q18. What is regression testing?
Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously. Regression Testing is important because of following reason:
- That the application works even after the alteration in the code were made.
- The original functionality continues to work as specified even after doing changes in the software application.
- The alteration to the software application has not introduced any new bugs.
Q19.What is data driven testing?
Data Driven is an automation testing part in which test input or output values, these values are read from data files. It is performed when the values are changing by the time. The different data files may include data pools, csv files, Excel files. The data is then loaded into variables in recorded or manually coded scripts. For data driven testing we use Parameterzing and Regular expression Technique.
Ex: To evaluate login functionality, we use different user name and password combinations, variables are used to access different username and password. The list of username and password are stored in a data table or excel sheet.
Q20. 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.
Post a Comment