100 Updated Quality Engineer Interview Questions
Q – 1 How to perform integration testing in Quality Engineering?
Ans- Integration testing is black box testing. Integration testing focuses on the interfaces between units, to make sure the units work together. For integration testing we ensure that all units testing of the each component is performed earlier. Integration testing begins only after the unit testing.
The purpose of integration testing is to ensure different components of the application interact with each other. So that, components work as per the customer requirements. Test cases are developed with the purpose of exercising the interfaces between the components. Integration testing is considered complete, when actual results and expected results are same.
Q – 2 How to perform regression testing performed manually in Quality Engineering?
Ans- We can perform regression testing manually, but it requires lots of effort. To choose the way of doing the regression testing is totally depends on the initial testing approach. If the initial testing approach was manual testing, then the regression testing is usually performed manually.
In case, if the initial testing approach was automated testing, then the regression testing is usually performed by automated testing. Automated regression testing is very easy task.
Q – 3 How to prepares the Test Plan without SRS in Quality Engineering?
Ans- To prepare a test plan directly without having SRS, When the Requirements and URD(User Requirement Document )are available to us. URD is very helpful to determine the requirement of the user. The SRS document only contains the requirement of the user, but tester can also determine the requirement form the product.
Without having SRS document we cannot estimate the Testing effort and cost of testing if we do not have SRS. SRS tell us on which platform our software is going to be used and on basis of this we perform the test on the application. Some time end user want to know what type of testing we are going to execute on the application for this we can send our test plan to the client.
Q – 4 Can you please explain the difference between responsibilities of Programmers and QA analyst?
Ans-
★ QA is concern for Process Quality and Programmers are concern for Product Quality.
★ QA ensure that the processes used for developing the product of high quality where as programmers used these processes so that end product is of good quality.
★ Processes are decided by QA. Programmers are supposed to follow the processes so that they can produce a good quality product.
★ Any issue found during execution of process by the programmers is communicated to the QA so that they can improve the process.
Q – 5 Which tools can used to support testing during development of application?
Ans-
★ Test management tools example: Quality Center, JIRA.
★ Defect management tool example: Bugzilla, Test Director.
★ Project management: Sharepoint.
★ Automation tools: QTP, RFT, WinRunner.
Q – 6 Which testing activities are automated in Quality Engineering?
Ans- ★ Functional tests:
Identify some P1 and P2 cases which are most critical for project success and operations and automate them. After every new build, these scripts will assure the fixes does not broke any of the critical functionality.
★ Regression test suites:
Test the need to be run after each build.
★ Performance tests:
Identical test the need to be run on different browser.
★ Stress tests
★ Load tests
Q – 7 List the main attributes of test automation in Quality Engineering?
Ans- Maintainability:
For each new release need to update the test automation suites.
Reliability:
Accuracy and repeat-ability of the test automation.
Flexibility:
Ease of working with all the different kinds of automation test ware.
Efficiency:
Total cost related to the effort needed for the automation.
Portability:
Ability of the automated test to run on different environments.
Robustness:
Effectiveness of automation on an unstable or rapidly changing system.
Usability:
Extent to which automation can be used by different types of user.
Q – 8 Which things may be go wrong in test automation?
Ans-
★ Ignoring automation, while planning the development phases.
★ In design Phase not choosing the right technology.
★ In coding Phase not automating the right test cases.
★ Tool selection might go wrong.
★ Test script not be updated when application is continuously changing.
★ Test data should be unique, if the same data is available on the application then the application will not accept the data that we are going to add via automation.
Q – 9 List the testing life-cycle phases?
Ans-
★ Test Planning (Test Strategy, Test Plan, Test Bed Creation)
★ Test Development (Test Procedures, Test Scenarios, Test Cases)
★ Test Execution
★ Result Analysis (compare Expected to Actual results)
★ Defect Tracking
★ Reporting
Q – 10 Define good code in Quality Engineering?
Ans- A code that works. The good code must not contain the defect or bug and is readable by other developers and easily maintainable. Organizations have coding standards all developers should follow, and also every programmer and software engineer has different ideas about what is best and what are too many or too few rules.
We need to keep in mind that excessive use of rules can decrease both productivity and creativity. Peer reviews and code analysis tools can be used to check for problems and enforce standards.
Q – 11 Which tests are performed on the web based application in Quality Engineering?
Ans- For web application we perform following time of test:
1) Functionality Testing.
2) Usability Testing.
3) Navigation Testing.
4) Configuration and Compatibility testing.
5) Reliability and Availability Testing.
6) Performance Testing.
7) Load and Stress Testing.
8) Security Testing
Q – 12 List the purposes of test strategy in Quality Engineering?
Ans-
1) To have a signed, sealed, and delivered document, where the document contains details about the testing methodology, test plan, and test cases.
2) Test strategy document tells us how the software product will be tested.
3) Test strategy document helps to review the test plan with the project team members.
4) It describes the roles, responsibilities and the resources required for the test and schedule.
5) When we create a test strategy document, we have to put into writing any testing issues requiring resolution.
6) The test strategy is decided first, before lower level decisions are made on the test plan, test design, and other testing issues.
Q – 13 How to choose which defect to remove in 1000000 defects in Quality Engineering?
Ans- First thing testers are not responsible for fixing the bug they are only responsible for debugging the bug and prioritizing those bugs. These bugs are now reported in bug report template with the severity and priority of the bug.
Tester assigns severity level to the defects depending upon their impact on other parts of application. Every bug has its severity and priority values assign by tester. If a defect does not allow you to go ahead and test the product, it is critical one so it has to be fixed as soon as possible.
We have 5 levels as:
★ Critical
★ High
★ Medium
★ Low
★ Cosmetic
Q – 14 Tell me how to create requirements test matrix template in Quality Engineering?
Ans- Step 1:
Find out number of requirements.
Step 2:
Find out number of test cases.
Step 3:
Create a table based on these. Let we have 10 requirements and 40 test cases, then we create a table of 11 rows and 41 columns.
Step 4:
On the first column of table copy all your 10 requirement numbers, and paste them into rows 2 through 11 of the table.
Step 5:
Now copy all 40 test case numbers, and paste them into columns 2 through 41 of the table.
Step 6:
Examine each of your 40 test cases, determine which of the 10 requirements they satisfy.
Q – 15 What is Time Estimation method for Testing Process in Quality Engineering?
Ans- Step 1:
Count number of use cases (NUC) of system
Step 2:
Set Avg. Time Test Cases(ATTC) as per test plan
Step 3:
Estimate total number of test cases (NTC)
Total number of test cases = Number of Use Cases X Avg. Test Cases per a use case
Step 4:
Set Avg. Execution Time (AET) per a test case
Step 5:
Calculate Total Execution Time (TET)
TET = Total number of test cases * AET
Step 6:
Calculate Test Case Creation Time (TCCT)
usually we will take 1.5 times of TET as TCCT
TCCT = 1.5 * TET
Step 7:
Time for Re-Test Case Execution (RTCE) this is for retesting
usually we take 0.5 times of TET
RTCE = 0.5 * TET
Step 8:
Set Report generation Time (RGT
usually we take 0.2 times of TET
RGT = 0.2 * TET
Step 9:
Set Test Environment Setup Time (TEST)
it also depends on test plan
Step 10:
Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer.
Q – 16 Which methodologies do you used to develop test cases in Quality Engineering?
Ans- Error Guessing:
The tester has to guess what fault might occur and to design the tests to represent them.
Equivalence Class Partitioning:
The input domain data is divided into different equivalence data classes; take few valid values with 2 invalid values. This is used to reduce the total number of test cases to a finite set of testable test cases.
Boundary value analysis:
Boundary value analysis testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain. Boundary value analysis is a next part of Equivalence.
Q – 17 Explain the difference between test strategy and test plan?
Ans-
★ Test plan is dynamic where as test strategy is static.
★ Test plan is prepared by the Test Lead where as Test Strategy is prepared by the company management.
★ Test strategy defines: methods and coverage criteria to be covered test completion criteria, prioritization of the test where as Test plan is a document describing the scope, approach, resources and schedule of intended test activities.
★ Test Strategy is a high level description of the test levels to be performed where as Test plan is written record of the test strategy and resource planning.
Q – 18 What is Top Down Approach in Quality Engineer?
Ans-
★ The top down approach is carried out with the help of the test stub. Test stub are the dummy programs. The Stub is called from the software component to be tested.
★ Tests top layer of controlling subsystem first. Then combine modules that are called by the tested modules and test resulted collection of modules.
★ Do this until all the modules are combined and tested.
Q – 19 What is Bottom Up Approach in Quality Engineer?
Ans- The bottom up approach testing approach is carried out with the help of the test driver. The test driver calls a component to be tested. The modules in the lower level of call hierarchy are tested independently. Then the next level modules are tested that call previously tested modules.
This is done repeatedly until all the modules are included in the testing. Bottom up testing stops when the top module in the call hierarchy is tested with all lower call hierarchy modules.
Q – 20 List the dimensions of the Risks step by step?
Ans- Schedule:
Unrealistic schedules. to develop a huge software in a single day.
Client:
Ambiguous requirements definition, requirement and not clear, changes in the requirement etc.
Human Resources:
Non-availability of sufficient resources with the skill level expected in the project.
System Resources:
Non-availability of procuring all critical computer resources either hardware and software tools or licenses for software will have an adverse impact.
Quality:
Compound factors like lack of resources along with a tight delivery schedule and frequent changes to requirements will have an impact on the quality of the product tested.
Q – 21 How to prioritize testing tasks within a project in Quality Engineering?
Ans-
★ Preparation of Test Plan.
★ Preparation of Test Cases.
★ Execution of the Test Cases.
★ Defect report and tracking.
★ Test Report Summary.
Q – 22 What are the roles of Bug Tracking System in Quality Engineering?
Ans-
★ Testers and developers can know the status of the bug at every stage.
★ Changes to the Status will be available to all team members.
★ Developers and Testers can easily interact with bugs.
★ Repetition of bugs will be avoided.
★ Easy to distribute the bug among the developer.
★ It will act as a centralized one for defects.
Q – 23 Do you know how to find all Bugs in first round of Testing?
Ans- There could be several reasons for not debugging the entire bug in the first round of testing process. Debugging the showstopper in the first or second build is almost impossible. A found defect can cover up the other defects in the application.
The thread which leads to on defect could be redirected to another defect, as the tester find the bug and lock that bug in report and after fixing of those bugs new bugs may also arises. It is difficult to keep testing on a known defective application. That is the reason we cannot find all the bug in first run and also we cannot perform Exhaustive testing.
Q – 24 Why Gantt Chart is used in Quality Engineering?
Ans- A Gantt Chart is used to represent a project schedule that includes duration of individual tasks or phases, their dependencies and ordering.
★ It displays the start and end points of each task and the percentage of completion of each task
★ It allows the planner to assess the duration of a project, identify the resources needed, and lay out the order in which tasks need to be performed.
★ It is useful in managing the dependencies between tasks.
★ Using Gantt chart each team member can view the product development schedule.
Q – 25 What is Use Case Testing in Quality Engineering?
Ans- The use case testing uses this use case to evaluate the application. So that, the tester can examines all the functionalities of the application. Use case testing cover whole application, tester performs this testing in step by step process to complete one task.
Q – 26 What is Use Case in Quality Engineering?
Ans- A use case is a description of the process which is performed by the end user for a particular task. Use case contains a sequence of step which is performed by the end user to complete a specific task or a step by step process that describe how the application and end user interact with each other. Use case is written by the user point of view.
Q – 27 Why we perform the Performance testing in Quality Engineering?
Ans- Performance Testing is performed to determine response time of the some components of the system perform under a particular workload. It is generally measured in terms of response time for the user activity. It is designed to test the overall performance of the system at high load and stress condition.
Q – 28 Why we perform the load testing in Quality Engineering?
Ans- The reason to perform the load testing is to determine response times of application processes and transactions to establish whether they are within acceptable time limit or not, as per user requirement. It also measures the capability of an application to function correctly under load by measuring the systems key performance indicators.
Q – 29 Explain the difference between test effectiveness and test efficiency?
Ans-
★ Test Efficiency is the ratio of number of test cases executed by unit of time (generally per hour).
★ It is the amount of code and testing resources required by a program to perform a particular function. Test Effectiveness evaluates the effect of the test environment on the application.
★ Test Effectiveness is a measure by the customer response on meeting product requirements where as Test Efficiency is a measure of optimum utilization of resources to create the Software product.
Q – 30 Described Agile Testing in Quality Engineering?
Ans- Agile Testing means to quickly validation of the client requirements and make the application of good quality user interface. When the build is released to the testing team, testing of the application is started to find the bugs. As a Tester, we need to focus on the customer or end user requirements.
We put the efforts to deliver the quality product in spite of short time frame which will further help in reducing the cost of development and test feedback’s will be implemented in the code which will avoid the defects coming from the end user.
Q – 31 Define the need of Test Plan document in Quality Engineering?
Ans- Test Plan tells the tester that what needs to be tested and how testing is going to be performed. Test plan also tells that what resources are needed for the execution of the test cases, timelines and risk associated with the test plan.
We can also perform the testing without test plan document, but first we have to select test Approach for the testing and go with testing. Many test plans are being created just for the sake of processes. Many tester use test plan documents when test plan document contains the some useful information.
Q – 32 Which factors are responsible for estimation of system integration test cycle and total integration time?
Ans-
★ Relative complexity of the modules.
★ Relative complexity of the interface between the modules.
★ Number of modules in the system.
★ Number of modules needed to be clustered together in each test cycle.
★ Whether the modules to be integrated have been adequately tested before.
★ Turnaround time for each test-debug-fix cycle.
Q – 33 What is paradigms for interfacing module?
Ans- Procedure Call Interface:
A procedure from one module calls to procedure of another module. The caller can pass data to the called procedure while calling and also the called procedure can pass data to the caller while returning control back to the caller procedure.
Shared Memory:
When a block of memory is shared between two modules. The memory block may be allocated by one of the two modules or third module of the same application.
Message Passing Interface:
One module generates a message and sends the message to another module. It helps in building up the communication between different process or modules.
Q – 34 Define Capability Maturity Model (CMM) in Quality Engineering?
Ans- Divided in five levels:
1) Initial:
The organization is characterized by an adhoc set of activities. The processes aren’t defined and success depends on individual effort and heroics.
2) Repeatable:
In this level some processes are repeatable, possibly with consistent results.
3) Defined:
In this level, we define all processes are documented for both management and engineering activities, and standards.
4) Managed:
Detailed measures of each process are defined and product quality data is routinely collected. Both process and products are quantitatively understood and controlled.
5) Optimizing:
In this we optimize the application by following improvement process.
Q – 35 List the benefits of Automated Testing in Quality Engineering?
Ans- Benefits of Automation Testing are below:
Consistency in testing.
Test interval reduction
Test engineer productivity.
Coverage of regression testing.
Re-usability of test cases.
Reduced software maintenance cost
Increased test effectiveness
Q – 36 Define random testing in Quality Engineering?
Ans-
★ The input domain is selected.
★ Test inputs are selected independently from the domain.
★ The system under test is executed on these inputs. The inputs constitute a random test set.
★ The results are compared to the system specification. The test is a failure if any input leads to incorrect results, otherwise it is a success.
Q – 37 What tests ensure in Quality Engineering?
Ans-
★ The number of parameters sent in a message agrees with the number of parameters expected to receive.
★ The parameter order in the message match the order expected.
★ The field sizes and data type match.
★ When a message is generated from stored data prior to being sent, the message truly reflects the stored data.
★ When a received message is stored, data copying is consistent with the received message.
Q – 38 Describe Monkey testing?
Ans-
Monkey testing is a type of Black Box Testing used mostly at the Unit Level. In this tester enter the data in any format and check the software is not crashing. In this testing we use Smart monkey and Dumb monkey.
★ Smart monkeys are used for load and stress testing, they will help in finding the bugs. They are very expensive to develop.
★ Dumb monkey, they are important for basic testing. They help in finding those bugs which are having high severity. Dumb monkey are less expensive as compare to Smart monkeys.
Q – 39 Described Traceability Matrix?
Ans- Trace-ability Matrix is a method used to validate the compliance of product with requirements for that product. The requirement is written in a row of the matrix and the columns of the matrix. Now they are used to identify how and where each requirement has been addressed.
It is in the form of table that correlates two base lined documents that require a many-to-many relationship. It is used with high level requirement and detailed requirement of the software product to the matching parts of high level design, detailed design, test plan, and test cases. The relationship to the source documents is required for both backward trace-ability and forward trace-ability.
Q – 40 Define what is Bug Triage?
Ans-
★ Ensure bug report completeness.
★ Analyze and assign bug to proper component.
★ Assign bug to proper bug owner.
★ Set appropriate bug priority.
★ Adjust bug severity properly.
Q – 41 Why test stub and test driver needed in Quality Engineering?
Ans-
★ 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.
Q – 42 Define test driver and test stub?
Ans- ★ 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.
Q – 43 What is the purpose of testing?
Ans- ★ Quality assurance, Verification and Validation,
★ To find the bugs before the product is released to customer.
★ To improve the quality of the product
★ The Purpose of Testing is to evaluate that the product is according to requirements
Q – 44 Tell me how you decide that you have tested enough?
Ans- ★ When there is no time and budget.
★ When maximum number of test cases are executed.
★ All the Requirements are mapped that is RTM is filled completely.
★ When Test coverage is more than 80%.
★ When bug rate falls below certain level.
Q – 45 Define Exploratory testing in Quality Engineering?
Ans- Exploratory testing means testing an application without a test plan and test script. In exploring testing test explore the application on the basis on his knowledge. The tester has no knowledge about the application previously. He explores the application like an end user and try to use it. While using the application his main motive is to find the bugs which are in the application.
Q – 46 Define Specification-driven testing in Quality Engineering?
Ans- Specification-driven testing means to test the functionality of software according to the user requirements. In this, tester inputs multiple data and monitors the outputs from, the test object. In this testing tester evaluate the showstopper bugs which break the major functionality of the application. This type of testing requires test plan and test.
Q – 47 Define Alpha testing in Quality Engineering?
Ans- 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.
Q – 48 Define Beta testing in Quality Engineering?
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 QA team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.
Q – 49 Why Regression Testing is important in Quality Engineering?
Ans- 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 – 50 Define 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.
Q – 51 Define Bug release in Quality Engineering?
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 – 52 Define Bug Leakage in Quality Engineering?
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 – 53 What is the reason behind to choosing the SDLC model for development of software?
Ans-
★ 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 – 54 Why lots of Quality Engineer choose automated testing over manual testing?
Ans- 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) Re-usability of Automation Script
4) Adaptability of test case for automation.
5) Exploitation of automation tool.
Q – 55 Describe the key challenges of software testing in Quality Engineering?
Ans-
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
) Lack of resources, tools and training
Q – 56 Define Release in Quality Engineering?
Ans- Release is a number given to install-able 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 – 57 Define Build in Quality Engineer?
Ans- Build is a number given to install-able software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.
Q – 58 Define severity of bug?
Ans- Severity is to concern with functionality of application. It deals with the impact of the bug on the application.
Q – 59 Define priority of bug?
Ans- Priority is to concern with application from the business point of view.
Q – 60 Define Validation in Quality Engineering?
Ans- Validation is a process of evaluating product during or at the end of the development process to determine whether product meets specified requirements.
Q – 61 Define Verification in Quality Engineering?
Ans- Verification is a process of evaluating steps which is followed up to development phase to determine whether they meet the specified requirements for that stage.
Q – 62 Described the role of QA in a project development?
Ans-
★ 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.
Q – 63 List the common problems with software automation?
Ans-
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
Q – 64 Do you know how much bug is affecting the functionality of the application?
Ans- 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 – 65 Described about bug life cycle?
Ans-
★ 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.
Q – 66 Can you please explain the difference between Retesting and Regression testing?
Ans-
★ 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 – 67 Why Testware is special in Quality Engineering?
Ans- Testware is special because it has:
1) Different purpose
2) Different metrics for quality and
3) Different users
Q – 68 Describe Testware?
Ans-
★ 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.
Q – 69 What are the benefits of destructive testing?
Ans-
★ Verifies properties of a material
★ Ensures compliance with regulations
★ Determines quality of welds
★ Helps you to reduce failures, accidents and costs
Q – 70 Tell me what is destructive testing?
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.
Q – 71 Can you please explain the difference between verification and validation?
Ans-
★ 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, walk-through 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.
Q – 72 What can you suggest to ensure quality of materials and products?
Ans- Basic procedure in quality engineering is Continuous Improvement. Describe involvement, method of data collection from observation and monitoring of production processes. Problem-solving skills are the key to success here and you will do well to mention your unique abilities in this area: Problems you solved, corrections you facilitated and improvements you initiated.
Q – 73 Tell me did you ever undertake staff training and instruction on Quality Assurance?
Ans- Training and instruction of staff regarding quality issues is necessary as part of quality control. If you have any experience in this field, describe the specific reason and subject of training. Underscore, without arrogance, your accomplishments with the group.
Q – 74 Do you know when to start QA in a project?
Ans- 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.
Q – 75 How would you describe 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 – 76 Define Quality Control?
Ans- Quality Control 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.
Q – 77 Define 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. QA tracks the outcomes and adjusts the process to meet the expectation.
Q – 78 How effective team-playing skills are?
Ans- Quality Engineers interact with employees at all levels, from minor suppliers to organization management. Describe a specific assignment where you had to use your communication skills, participate in a group endeavor or manage/lead a team.
Discuss your routine communication with all levels of management, quality managers and inspectors, development engineering divisions, operations and QA testing staff.
Q – 79 Tell me about your previous interactions with customers. How do you handle customer complaints?
Ans- Quality engineers can serve as the link between customers and suppliers. When a customer complains about product quality, the engineer must then solve the problem between the customer, the company, and its affiliates, including material and parts suppliers. Briefly describe some interesting problems that you have successfully tackled.
Q – 80 Describe the various responsibilities and roles of a quality engineer?
Ans- Discuss not only quality control, QA tests, and monitoring of various kinds (materials, products, electrical systems), but also other related tasks that a QA engineer might be responsible for: improvement processes, quality-oriented staff training, and quality-related customer services.