QTP Questions
- Find the Cyclometric complexity on the following pseudo code
Do while records remain read record;
if record field#1=0 then process record;
store in buffer;
incremental counter;
store in file. reset counter;
end if end do please let me know the procedure too.
A. The answer for this is 3. - Usecases and noun lists are associated with the following Requirement analysis methodologies 1.Information engineering 2.Object oriented analysis 3.Structural analysis 4.Functional analysis. Usecases are associated with Functional Analysis.
- In which stage more defects found means analysis, design, coding, testing and maintenance?
- What are the test methodologies?
- What r the GUI Test Cases for calculator?
- Exactly what is the purpose of configuration management tool? Also give some examples?
- What is Buddy testing?
- How to test background color and dynamic images during runtime?
- When to Stop Testing?
- What is SEI?
- What is test log? Tell the process?
- Explain me about test scenarios? How will you write it?
- Overall what percentage of positive and negative testcases would you write?
- Actually how many positive and negative testcases will write for a module?
- Will you write a test plan in all phases?
- What is the formal technical review?
3 formula's to calculate Cyclometric complexity. You can choose either of them...
C.C = No of bounded regions +1
C.C = No of edges - No of nodes +1
C.C = No of predicate Nodes +1
Now let's consider the first formula to calculate as the rest 2 diagrams require flow graphs to be drawn. Do while loop forms 1 bounded region and IF condition forms 1 bounded region.
So as per this formula, C.C = No of bounded regions + 1
2 + 1 = 3.
Reasons not to automate.
a.No formal test plan.
b.No Design document.
c.Testing budget is minimal.
d.All of the above.
A. d
A. Sorry to say that more defects are from requirements phase.
Requirements 56%.
Design 26%.
Coding 7%.
Remaining testing.
A. Test Methodology differs from company to company and project to project. But all of them will follow the same life cycle with a little bit of variance in the micro level.
In a macro level Test Methodology includes:
Test Initiation,Test Planning,Test Design,Test Execution,Defect Management & Test Closure
A. 1. Check for all the buttons are available r not.
2. Check the screen for displaying.
3. Check consistency of all the buttons.
4. Check the spelling for the objects.
A. To cover the process controlling, coordinating, Track code, change requirement made to them CMM used to store our test cases and to store Test plans which are other documents that are related to testing and also used to give status for our test cases which we executed.
A. Buddy testing, a very effective and efficient testing practice, for superior code. Our programmers are more efficient and get things right the first time using buddy testing. This is a simple concept to ensure that each software feature goes through a quick sanity check of a QA engineer before it is checked-in. Every developer is associated with a "buddy" tester who does this sanity check (typically of the user interface, which is not covered completely through unit test cases). Essentially, we create the test scenarios before the code is written, and so quality is assured at the unit test levels itself. Risk analysis and identification occurs early greatly reducing the number of bugs in the final product, through walkthroughs and periodic close inspections and interactions between tester and developer.
A. It is possible only in web applications only.by using check points we have to test the back ground colour and dynamic images for eg: Yahoomail page back ground colour is blue
A. In many condition we have to stop Testing:
1.If Specification is not proper.
2.If so many show stopper bugs are there.
3.Functionality is not meeting to the Specification.
4.Environment is not proper to test (System Environment).
5.When the allocated time exceeds, allocated cost exceeds.
6.When deadlines are met.
7.Showstoper kind of issue is found.
8.Bug rates fall below certain level.
9.When test cases are complete.
A. Software Engineering Institute.
Software Engineering Institute is Carneige Mellon University, they developed CMMI model which is popularly followed by software organisations as Standard.
A. A test log is nothing but, what are the test cases we r executed, in what order we executed, who executed that test cases and what is the status of the test case(pass/fail).
A. Test scenario is a series of actions that the user might perform on the application or tester might plan to do. Ex: drawing money from ATM is a test scenario, similarly checking account is a scenario.
A. That depends on the screen. Most of the times, I will verify for the -ve test conditions, but compared to positive testing in negative testing we pump up more number of different sets of data with an intention of finding the bug.
A. That depends on the module & complexity of logic. For every test case, we can identify +ve and -ve points. Based on the criteria, we will write the test cases. If it is crucial process or screen,we should check the screen in all the boundary conditions.
A. Test Plan will be given by the Test Lead. As a Tester, I did not get a chance to write the test plan. Test Plan in the sense, it explains about the procedure you follow for the testing. What is the testing environment, where do you get the updated code, how do you compile and build your code and test the application. It will be specified in the document.
A. Technical review should be done by the team of members. The document which is going to be reviewed, who has prepared and reviewers should sit together and do the review of that document. It is called Peer Review. If it is a technical document, it can be called as formal Technical review, I guess. It varies depends on the company policy.
