Top Quality Analyst Interview Questions
Q – 1 What is the difference between alpha and beta testing?
Ans-
★ Alpha testing is performed by the In-House developers. After alpha testing the software is handed over to software quality assurance team, for additional testing in an environment that is similar to the client environment.
★ Beta testing 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 quality assurance team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.
Q – 2 Explain the difference between bug leakage and bug release?
Ans- 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 previous build then this is called as Bug Leakage.
Bug release:
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.
Q – 3 Can you please explain the difference between build and release?
Ans-
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.
Example: “9.4.123.2” (Release Number.Version Number.Build Number.Patch Number)
Q – 4 What is the difference between severity and priority of bug?
Ans- Priority:
Concern with application from the business point of view.
Like:
How quickly we need to fix the bug?
How soon the bug should get fixed?
Severity:
Concerns with functionality of application. It deals with the impact of the bug on the application.
Q – 5 What does software development life cycle include?
Ans- Software development life cycle includes the following different stages:
★ Requirement phase
★ Design phase
★ Coding (programming)
★ Testing
★ Release (Production)
★ Maintenance (Support)
Q – 6 What is software development life cycle?
Ans- The systems (or software) development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.
Q – 7 what does use case include?
Ans- Use case includes cover page, revision history, table of contents, floe of events (normal flow and alternative flow), exceptions, special requirements, pre-conditions and post-conditions.
Q – 8 Can you tell me what a use case is?
Ans- A use case is a document that describes the user action and system response for a particular functionality.
Q – 9 What does test case include?
Ans- A test case includes test case ID, steps description, expected output, actual output, pass/fail, remarks.
Q – 10 What is a Test Case?
Ans- A Test Case is a document that describes step by step process how to test the application.
Q – 11 What does test plan include?
Ans- A Test Plan includes Heading, Revision History, Table of Contents, Introduction, Scope, Approach, Overview, different types of testing that will be carried out, what software and hardware will be required, issues, risks, assumptions and sign off section.
Q – 12 What is a Test Plan?
Ans- A Test Plan is a document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks and who will do each task (roles and responsibilities) and any risks and its solutions.
Q – 13 Tell me about beta testing?
Ans- Beta testing 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 quality assurance team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.
Q – 14 Please tell me what is alpha testing?
Ans- Alpha testing is performed by the IN-House developers. After alpha testing the software is handed over to software quality assurance team, for additional testing in an environment that is similar to the client environment.
Q – 15 Give an example of data driven testing?
Ans-
Example:
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.
Q – 16 Do you have any idea about data driven testing?
Ans- 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.
Q – 17 What is regression testing?
Ans- 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.
Q – 18 Explain bug release?
Ans- 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.
Q – 19 Explain bug leakage?
Ans- 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 previous build then this is called as Bug Leakage.
Q – 20 Tell us what is the basis for choosing the SDLC model for development of software?
Ans- 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.
Q – 21 Do you know why do we choose automated testing over manual testing?
Ans- The reasons for choosing automation testing over manual testing are following:
★ Frequency of use of test case
★ Time Comparison (automated script run much faster than manual execution.)
★ Re-usability of Automation Script
★ Adaptability of test case for automation
★ Exploitation of automation tool
Q – 22 Explain what are the key challenges of software testing?
Ans- Following are some challenges of software testing
★ Application should be stable enough to be tested
★ Testing always under time constraint
★ Understanding requirements, Domain knowledge and business user perspective understanding
★ Which tests to execute first?
★ Testing the Complete Application
★ Regression testing
★ Lack of skilled testers
★ Changing requirements
★ Lack of resources, tools and training
Q – 23 What is release?
Ans- 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 that are using.
Q – 24 What is build?
Ans- 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.
Q – 25 What is the role of quality assurance in a project development?
Ans- Quality assurance team assures the quality by monitor the whole development process. Quality assurance tracks the outcomes and adjusting process to meet the expectation.
The role of quality assurance is discussed below:
★ Quality assurance team is responsible for monitoring the process to be carried out for development.
★ Responsibilities of quality assurance team are planning testing execution process.
★ Quality assurance Lead creates the time tables and agrees on a Quality Assurance plan for the product.
★ Quality assurance team communicated quality assurance process to the team members.
★ Quality assurance team ensures trace ability of test cases to requirements.
Q – 26 Tell me what are the common problems with software automation?
Ans- Software problems are listed below:
★ Purchasing the license of tool (QTP, selenium, QC, LR)
★ Lack of skilled Tester to run the tool
★ Expectation that automated tests will find a lot of new defects
★ Maintenance of automated tests
★ Technical problems of tools
Q – 27 What is severity of bug?
Ans- Severity of bug concerns with functionality of application. It deals with the impact of the bug on the application.
Q – 28 Give some examples of severity and priority of bug?
Ans- Examples:
★ 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.
Q – 29 What is priority of bug?
Ans- Priority of bug concerns with application from the business point of view.
Like:
How quickly we need to fix the bug?
How soon the bug should get fixed?
Q – 30 Tell us the difference between Retesting and Regression testing?
Ans- 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.
Q – 31 Please tell us what is testware?
Ans- The test-ware is:
★ The subset of software which helps in performing the testing of application.
★ Test-ware 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.
★ Test-ware is term given to combination of all utilities and application software that required for testing a software package.
Test-ware is special because it has:
1) Different purpose
2) Different metrics for quality and
3) Different users
Q – 32 Tell me what is destructive testing, and what are its benefits?
Ans- 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
Q – 33 Can you please explain the difference between smoke testing and sanity Testing?
Ans- 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 functions 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 functions.
Q – 34 When to start quality assurance in a project?
Ans- A good time to start the quality assurance is from the beginning of the project start-up. This will lead to plan the process which will make sure that product coming out meets the customer quality expectation.
Quality assurance 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.
Q – 35 Define software testing?
Ans- 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.
Q – 36 Describe quality control?
Ans- Concern with the quality of the product. Quality control finds the defects and suggests improvements. The process set by quality assurance is implemented by quality control. The quality control is the responsibility of the tester.
Q – 37 Describe quality assurance?
Ans- Quality assurance refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. Quality assurance tracks the outcomes and adjusts the process to meet the expectation.
Q – 38 Describe the role of software quality analyst in terms of the test plan-scope of work, monitoring reliability and project implementation?
Ans- Clarify in a specific and brief manner how you determine the timing for system testing and what to test. Like:
What point do you finalize the testing at?
Q – 39 Have you conducted audits on a regular basis?
Ans- If yes, describe the goals of the audit, how you have monitored the audit findings and how you have controlled the corrective actions.
Q – 40 Describe bug life cycle?
Ans- Bug life cycle consists of several statuses of an error during its life cycle such as: open, deferred, rejected, solved, fixed, reopen, and closed. You can talk about the process flow and how you monitor and determine the status at various points.
Q – 41 What is a gaga R & R?
Ans- R & R stands for reproducibility and repeatability. It is a system measurement error that determines the percentage of error, the type of error and its affects on the system.
Q – 42 What is defect?
Ans- Defect is a problem in the application algorithm or the mechanism that leads to consistent failure or an error that requires a massive change.
Q – 43 What is Bug?
Ans- Bug is a deviation from the expected result that can be fixed and solved.
Q – 44 What are the quality analyst software tools, automation tools and statistical software you use?
Ans- Provide lists of software such as: SAS and SWOT Manager or any software and automated testing emulation system which you have used. You may also clarify the differences between them, and explain how these tools enhance reliability.
Q – 45 What is the first test in software testing process?
Ans- Unit testing is the first test that is usually done by the developers.
Q – 46 What is the difference between verification and validation?
Ans- Verification is based on verifying the functionality of a new system while validation is based on testing scenarios and specific cases of a new system.
Q – 47 What is the meaning of trace-ability matrix?
Ans- A trace-ability matrix is used to cross check the test scripts per specified requirements of test cases.
Q – 48 What is the role of communication skills in the career of a quality analyst?
Ans- Quality analysts report to management and are able to make effective presentations of the situations or the problems, and the possible ways to fix problems.
They also interact with all levels of employees, clients, and suppliers and their written and verbal skills must be first rate to be effective.
Q – 49 Do you have experience working with people as a quality analyst?
Ans- All quality analysts work with people. Analyzing the production process means analyzing the people working on production, as well as the technology involved. Quality analysts are able to interact effectively with employees at all levels of the production process. They also report to department and company managers and often personally meet clients or suppliers.
Q – 50 Tell us the important characteristics of a successful quality analyst?
Ans- A Quality analyst is highly trained, highly educated professional. It has outstanding analytical ability and extensive knowledge. It learns quickly and are able to expertly analyze current market demands and company-specific conditions. It is also very creative, because it solves problems by developing company-specific testing and improvement methods.
Q – 51 How do a quality analyst use testing methods within his job?
Ans- A Quality analyst develops ways to test a specific company’s production process. He can also train other company personnel and any other quality inspectors to use this testing method.
Q – 52 What exactly does a quality analyst analyze in a company?
Ans- To maintain product quality, analysts look at the current finished product and at the production process, from development to marketing. They put that in the context of the market and company goals and possibilities. They analyze this information for any problems and opportunities at improvement.
Q – 53 Who is quality analyst?
Ans- A quality analyst makes sure company products and services remain of the highest quality at all times, in all stages of the production process.