ISTQB Sample Question and Answers- #1

Please scroll down to find the answers....

Q1. An input field takes the year of birth between 1900 and 2004. 
The boundary values for testing this field are:
a.) 0,1900,2004,2005
b.) 1900, 2004
c.) 1899,1900,2004,2005
d.) 1899, 1900, 1901,2003,2004,2005


Q2. Which one of the following are non-functional testing methods?
a. System testing
b. Usability testing
c. Performance testing
d. Both b & c



Q3. Which of the following tools would be involved in the automation of regression test?
a. Data tester
b. Boundary tester
c. Capture/Playback
d. Output comparator.

Q4. Incorrect form of Logic coverage is:
a. Statement Coverage
b. Pole Coverage
c. Condition Coverage
d. Path Coverage

Q5. Which of the following is not a quality characteristic listed in ISO 9126 Standard?
a. Functionality
b. Usability
c. Supportability
d. Maintainability

Q6. To test a function, the programmer has to write a _________, which calls the function to be tested and passes it test data.
a. Stub
b. Driver
c. Proxy
d. None of the above

Q7. Boundary value testing
a. Is the same as equivalence partitioning tests
b. Test boundary conditions on, below and above the edges of input and output equivalence classes
c. Tests combinations of input circumstances
d. Is used in white box testing strategy

Q8. Pick the best definition of quality
a. Quality is job one
b. Zero defects
c. Conformance to requirements
d. Work as designed

Q9. Fault Masking is
a. Error condition hiding another error condition
b. Creating a test case which does not reveal a fault
c. Masking a fault by developer
d. Masking a fault by a tester

Q10. One Key reason why developers have difficulty testing their own work is:
a. Lack of technical documentation
b. Lack of test tools on the market for developers
c. Lack of training
d. Lack of Objectivity

Q11. During the software development process, at what point can the test process start?
a. When the code is complete
b. When the design is complete
c. When the software requirements have been approved
d. When the first code module is ready for unit testing

Q12. In a review meeting a moderator is a person who
a. Takes minutes of the meeting
b. Mediates between people
c. Takes telephone calls
d. Writes the documents to be reviewed

Q13. Given the Following programIF X <>= ZTHEN Statement 2;ENDMcCabe’s Cyclomatic Complexity is :
a. 2
b. 3
c. 4
d. 5

Q14. How many test cases are necessary to cover all the possible sequences of statements (paths) for the following program fragment? Assume that the two conditions are independent of each other : -…………if (Condition 1)then statement 1else statement 2fiif (Condition 2)then statement 3fi…………
a. 2 Test Cases
b. 3 Test Cases
c. 4 Test Cases
d. Not achievable


15. Acceptance test cases are based on what?

a. Requirements
b. Design
c. Code
d. Decision table

Q16. How much testing is enough?
a. This question is impossible to answer
b. This question is easy to answer
c. The answer depends on the risk for your industry, contract and special requirements
d. This answer depends on the maturity of your developers

Q17. A common test technique during component test is
a. Statement and branch testing
b. Usability testing
c. Security testing
d. Performance testing

Q18. Statement Coverage will not check for the following:
a. Missing Statements
b. Unused Branches
c. Dead Code
d. Unused Statement

Q19. Independent Verification & Validation is
a. Done by the Developer
b. Done by the Test Engineers
c. Done By Management
d. Done by an Entity Outside the Project’s sphere of influence

Q20. Code Coverage is used as a measure of
a. Defects
b. Trends analysis
c. Test
d. Time Spent Testing

Answers:--
1. C
2. D
3. C
4. B
5. C
6. B
7. B
8. C
9. A
10. D
11. C
12. B
13. B
14. A
15. A
16. C
17. A
18. A
19. D
20. C

Effective way of reporting Bug- Defect report

According to the standard way of Defect profile document format:

Bug Title: 

Title should be short, precise and point the issue correctly.

Bug Description: 

Though the title reflects the issue in short, define the bug in few lines

which gives brief description

Steps to reproduce:

Here clearly mention the steps where you face the error and what are

the steps to be reproduced for it. Mention the steps right from invoking

a browser , entering application url to the place where issue arised.

Screen shots:

Screen shots play an important role for effective bug report.Try to attach

 the screen shots which make others to understand easily on looking it.

Sometime the issue may be over looked while reproducing, hence attach

the screen shots for necessary bugs.

Make an habit of it.

Details:

Some data like environmental details may also help developers to understand

what exactly is the cause by knowing the environment. Environment details

such as Operating System, Browser and its version etc.. Some browsers may

not support some features and some issues may also does not occur in some browsers.

Hence this information helps developers to resolve issue sooner.

Shot directly:

Never report against any single person directly as XXX person developed this .

Priority:
When bug should be fixed? Priority is generally set from P1 to P5. P1 as “fix the bug with highest priority” and P5 as ” Fix when time permits”.

Severity:
This describes the impact of the bug.
Types of Severity:

• Blocker: No further testing work can be done.
• Critical: Application crash, Loss of data.
• Major: Major loss of function.
• Minor: minor loss of function.
• Trivial: Some UI enhancements.
• Enhancement: Request for new feature or some enhancement in existing one.

Current Result: 

What is the actual result on running above steps i.e. the bug behavior

Expected:

How application should behave on above mentioned steps.

Environment

This helps to answer question that the assignee may have.

Product: In which product you found this bug.

Version: The product version if any.

Component: These are the major sub modules of the product.

Platform: Mention the hardware platform where you found this bug. The various platforms like ‘PC’, ‘MAC’, ‘HP’, ‘Sun’ etc.

Operating system: Mention all operating systems where you found the bug. Operating systems like Windows, Linux, Unix, SunOS, Mac OS. Mention the different OS versions also if applicable like Windows NT, Windows 2000, Windows XP etc.

Simple Language :

Use simple language while explaining about any issue which is understood by anyone