Certified Quality Engineer Interview Preparation Guide

Download PDF

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.

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.

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.

★ 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.

★ Test management tools example: Quality Center, JIRA.
★ Defect management tool example: Bugzilla, Test Director.
★ Project management: Sharepoint.
★ Automation tools: QTP, RFT, WinRunner.

★ 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

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.

★ 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.

★ 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

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.

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

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.

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

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.

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.

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.

★ 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.

★ 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.

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.

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.

★ Preparation of Test Plan.
★ Preparation of Test Cases.
★ Execution of the Test Cases.
★ Defect report and tracking.
★ Test Report Summary.

★ 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.

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.

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.

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.