Few Interesting Questions for ISTQB

I regularly follow the ISTQB group.I found some interesting questions which i have gathered for further knowledge.

Here we go:

The differnce between the integration test cases and system test case ?

integration test happens between the components / units of the
application once they get built; and system testing happens once
integration testing of all the components happens properly.
System testing is nothing but testing the system as a Whole!


Static analysis tools

Static analysis tools applied to source code can enforce coding standards, but if applied to existing code may generate a lot of messages. Warning messages do not stop the code being translated into an executable program, but should ideally be addressed so that maintenance of the code is easier in the future. A gradual implementation with initial filters to exclude some messages would be an effective approach.


IEEE-829 in brief
IEEE 829 standard for software testing documentation
One of the challenges facing software testers has been the availability of an agreed set of document standards and templates for testing. The IEEE 829 provides an internationally recognised set of standards for test planning documentation.

IEEE 829 has been developed specifically with software testing in mind and is applicable to each stage of the testing life cycle including system and acceptance testing.

Types of Document
The IEEE 829 standard covers 8 document types.

Test specification
1.Test Plan: Covers how the testing will be managed, scheduled and executed.
2.Test Design Specification: defines logically what needs to be tested by examining the requirements or features. Then these requirements can be converted into test conditions.
3.Test Case Specification: Converts the test conditions into test cases by adding real data, pre-conditions and expected results
4.Test Procedure: Describes in practical terms how the tests are run.
5.Test Item Transmittal Report: Specify the items released for testing.Test execution
6.Test Log: Is an audit trail that records the details of tests in chronologically.
7.Test Incident Report: Record details of any unexpected events and behaviours that need to be investigated.
Test reporting
8.Test Summary Report: Summarise and evaluate tests.

negative testing is basically " test to fail " attitude.

hence a sample scenario for negative testing in notepad:
open notepad
type " this app can break"
then save ur notepad and close.
then when u reopen u cannot view the same content(it wil be corrupted)
that is in notepad if u type a cotent in this format 4 - 3 -3 -5 (for ex: this app can break) then
it doesnt work as intended

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 1
else statement 2
if (Condition 2)
then statement 3
a.2 Test Cases
b.3 Test Cases
c.4 Test Cases
d.Not achievable

to solve this we need to take
1.Condition 1 true and condition 2 true value this will execute statement 1 and statement 3
2.Condition 1 false and condition 2 dont care ...this will execute statement 2

so we need 2 sets of testcases to solve this.
Testing Principle - Testing is context dependent
Testing is done differently in different contexts. For example, safety-critical software is
tested differently from an e-commerce site.
Postal rates for 'light letters' are 25p up to 10g,35p up to 50g plus an extra 10p for each additional 25g up to 100g.

Which test inputs(in grams) would be selected using equivalence partitioning?????


Answer is b....

Hope these helps. Let me know if these are helping me.
Few Interesting Questions for ISTQB Few Interesting Questions for ISTQB Reviewed by Animesh Chatterjee on July 18, 2009 Rating: 5

No comments:

Powered by Blogger.