Skip to main content

ISEB-ISTQB Sample Exam Paper 57

When a tester executes a test and observes behaviour that differs from the specification, this is called a: a) defect b) error c) failure d) mistake e) fault Which of the following best describes regression testing? v) Testing to ensure unchanged areas still work w) Testing after a fix x) Testing after environment changes y) Testing after code refactoring z) Testing only at the end of the project a) v, w & y are true b) v & w are true c) v, w, x & y are true d) w & z are true e) all are true Which of the following is NOT included in IEEE 829 test documentation? a) Test summary report b) Test design specification c) Test incident report d) Test risk assessment e) Test log Testing should be stopped when: a) All planned tests are executed b) The exit criteria have been met c) No more defects are being found d) Time runs out e) Both b and c ...
Post a Comment

What is Random Testing?


Random Testing

 
 Random Testing uses a model of the input domain of the component that defines the set of all possible input values.  The input distribution (normal, uniform, etc.) to be used in the generation of random input values shall be based on the expected operational distribution of inputs.  Where no knowledge of this operational distribution is available then a uniform input distribution shall be used.

Test cases shall be chosen randomly from the input domain of the component according to the input distribution.

A test case shall comprise the following:

-     the input(s) to the component
 
-     the expected outcome of the test case.

The input distribution used for the test case suite shall also be recorded.
 

Comments

  1. Anonymous15 October 2012 at 02:35

    I found some cool exam papers for ISEB Software Testing which has all the questions and answers and full explanation for Random Testing @ www.iseb-sofwaretesting.weebly.com

    Randy

    ReplyDelete
  2. Solomon3431 October 2012 at 15:43

    "Random testing is a form of functional testing that is useful when the time needed to write&run directed tests is too long (or the complexity of the problem makes it impossible to test every combination). Release criteria may include a statement about the amount of random testing that is required. For example, we have a requirement that there should be no random failures for 2 weeks prior to release (that is 2 weeks of continuous random testing on 50 workstations)."

    Source: http://c2.com/cgi/wiki?RandomTesting

    ReplyDelete

Post a Comment