Post is pinned.Post has attachment
Download Your ISTQB Dumps-->
http://iseb-software-testing.co.uk
Photo

ISTQB Dumps, Exam Paper 10, ISEB ISTQB Foundation Software Testing

1. Choose the standard for software component testing:
a) BS7925-1
b) ISO9000
c) BS7925-2
d) DO-178B
e) IEEE 829

2. Which of these is not part of the fundamental test process?
a) planning
b) check completion
c) post project reviews
d) specifying tests
e) executing tests

3. A fault is defined as:
a) a deviation from expected delivery or service
b) a manifestation of an error in software
c) a malfunction resulting from the software being run
d) a mistake made by the developer
e) a human error made by the developer

4. A regression test:
a) is only run once
b) will always be automated
c) will help ensure unchanged areas of the software have not been affected
d) will help ensure changed areas of the software have not been affected
e) can only be run during user acceptance testing

5. Match the following terms with the following definitions
q) Planning
r) Specifying
s) Execution
t) Recording
u) Check completion
v) Determine whether there are any faults
w) Specify any exceptions to the strategy
x) Create test inputs and expected results
y) Running the most important tests first
z) Deciding whether we can stop testing
a) q=w; r=v; s=y; t=x; u=z
b) q=w; r=z; s=v; t=y; u=x
c) q=x; r=w; s=y; t=v; u=z
d) q=w; r=x; s=y; t=v; u=z
e) q=x; r=w; s=v; t=z; u=y

6. If an expected result is not specified then:
a) it is still worthwhile to run the test
b) we cannot run the test
c) it may be difficult to repeat the test
d) it may be difficult to determine if the test has passed or failed
e) we cannot automate the user inputs

7. Which statement about faults is false?
a) a fault can cause a failure
b) a fault is when something goes wrong with the system
c) a fault can be found in test documentation
d) a fault is also known as a bug or a defect
e) a fault is a manifestation of an error in the software

8. Which of the following are valid reasons for testing being necessary:
1. there are faults in the software
2. it assesses the quality of the software
3. it is part of the development lifecycle
4. it finds out about the reliability of the software
5. it helps avoid being sued by customers
a) All the above are valid reasons why testing is necessary
b) 1,2,3 are valid reasons; 4 & 5 are not
c) 1& 2 are valid reasons; 3,4,5 are not
d) 1,2,3,4 are valid reasons; 5 is not
e) 1,2,4,5 are valid reasons; 3 is not

9. Which of the following could be a reason for a failure?
1. testing fault
2. software fault
3. design fault
4. environment fault
5. documentation fault
a) 2 is a valid reason: 1,3,4 & 5 are not
b) 1 & 2 are valid reasons; 3,4,5 are not
c) 1,2,3,4 are valid reasons; 5 is not
d) 1,2,3 are valid reasons; 4 & 5 are not
e) All of them are valid reasons for failure

10. Tests are prioritised so that:
a) you shorten the time required for testing
b) you do the best testing in the time available
c) you do more effective testing
d) you find more faults
e) you complete all the planned testing
-
#ISTQB #ISTQBDUMPS #ISEB #SOFTWARETESTING
-
Software Testing Blog
https://iseb-software-testing.blogspot.com
-
Download ISTQB Dumps-->
http://iseb-software-testing.co.uk

Post has attachment
ISTQB Dumps, Exam Paper 3, ISEB ISTQB Foundation Software Testing

1 We split testing into distinct stages primarily because:
a) Each test stage has a different purpose.
b) It is easier to manage testing in stages.
c) We can run different tests in different environments.
d) The more stages we have, the better the testing.

2 Which of the following is likely to benefit most from the use of test tools providing test capture and replay facilities?
a) Regression testing
b) Integration testing
c) System testing
d) User acceptance testing

3 Which of the following statements is NOT correct?
a) A minimal test set that achieves 100% LCSAJ coverage will also achieve 100% branch coverage.
b) A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.
c) A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage.
d) A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage.

4 Which of the following requirements is testable?
a) The system shall be user friendly.
b) The safety-critical parts of the system shall contain 0 faults.
c) The response time shall be less than one second for the specified design load.
d) The system shall be built to be portable.

5 Analyse the following highly simplified procedure:
Ask: “What type of ticket do you require, single or return?”
IF the customer wants ‘return’
Ask: “What rate, Standard or Cheap-day?”
IF the customer replies ‘Cheap-day’
Say: “That will be £11:20”
ELSE
Say: “That will be £19:50”
ENDIF
ELSE
Say: “That will be £9:75”
ENDIF
Now decide the minimum number of tests that are needed to ensure that all
the questions have been asked, all combinations have occurred and all
replies given.
a) 3
b) 4
c) 5d) 6
6 Error guessing:
a) supplements formal test design techniques.
b) can only be used in component, integration and system testing.
c) is only performed in user acceptance testing.
d) is not repeatable and should not be used.

7 Which of the following is NOT true of test coverage criteria?
a) Test coverage criteria can be measured in terms of items exercised by a test suite.
b) A measure of test coverage criteria is the percentage of user requirements covered.
c) A measure of test coverage criteria is the percentage of faults found.
d) Test coverage criteria are often used when specifying test completion criteria.

8 In prioritising what to test, the most important objective is to:
a) find as many faults as possible.
b) test high risk areas.
c) obtain good test coverage.
d) test whatever is easiest to test.
9 Given the following sets of test management terms (v-z), and activity descriptions (1-5), which one of the following best pairs the two sets?
v – test control
w – test monitoring
x - test estimation
y - incident management
z - configuration control

1 - calculation of required test resources
2 - maintenance of record of test results
3 - re-allocation of resources when tests overrun
4 - report on deviation from test plan
5 - tracking of anomalous test results

a) v-3,w-2,x-1,y-5,z-4
b) v-2,w-5,x-1,y-4,z-3
c) v-3,w-4,x-1,y-5,z-2
d) v-2,w-1,x-4,y-3,z-5

10 Which one of the following statements about system testing is NOT true?
a) System tests are often performed by independent teams.
b) Functional testing is used more than structural testing.
c) Faults found during system tests can be very expensive to fix.
d) End-users should be involved in system tests.

11 Which of the following is false?
a) Incidents should always be fixed.
b) An incident occurs when expected and actual results differ.
c) Incidents can be analysed to assist in test process improvement.
d) An incident can be raised against documentation.

12 Enough testing has been performed when:
a) time runs out.
b) the required level of confidence has been achieved.
c) no more faults are found.
d) the users won’t find any serious faults.

13 Which of the following is NOT true of incidents?
a) Incident resolution is the responsibility of the author of the software under test.
b) Incidents may be raised against user requirements.
c) Incidents require investigation and/or correction.
d) Incidents are raised when expected and actual results differ.

14 Which of the following is not described in a unit test standard?
a) syntax testing
b) equivalence partitioning
c) stress testing
d) modified condition/decision coverage

15 Which of the following is false?
a) In a system two different failures may have different severities.
b) A system is necessarily more reliable after debugging for the removal of a fault.
c) A fault need not affect the reliability of a system.
d) Undetected errors may lead to faults and eventually to incorrect behaviour.

16 Which one of the following statements, about capture-replay tools, is NOT correct?
a) They are used to support multi-user testing.
b) They are used to capture and animate user requirements.
c) They are the most frequently purchased types of CAST tool.
d) They capture aspects of user behaviour.

17 How would you estimate the amount of re-testing likely to be required?
a) Metrics from previous similar projects
b) Discussions with the development team
c) Time allocated for regression testing
d) a & b

18 Which of the following is true of the V-model?
a) It states that modules are tested against user requirements.
b) It only models the testing phase.
c) It specifies the test techniques to be used.
d) It includes the verification of designs.

19 The oracle assumption:
a) is that there is some existing system against which test output may be checked.
b) is that the tester can routinely identify the correct outcome of a test.
c) is that the tester knows everything about the software under test.
d) is that the tests are reviewed by experienced testers.

20 Which of the following characterises the cost of faults?
a) They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.
b) They are easiest to find during system testing but the most expensive to fix then.
c) Faults are cheapest to find in the early development phases but the most expensive to fix then.
d) Although faults are most expensive to find during early development phases, they are cheapest to fix then.

21 Which of the following should NOT normally be an objective for a test?
a) To find faults in the software.
b) To assess whether the software is ready for release.
c) To demonstrate that the software doesn’t work.
d) To prove that the software is correct.

22 Which of the following is a form of functional testing?
a) Boundary value analysis
b) Usability testing
c) Performance testing
d) Security testing

23 Which of the following would NOT normally form part of a test plan?
a) Features to be tested
b) Incident reports
c) Risks
d) Schedule

24 Which of these activities provides the biggest potential cost saving from the use of CAST?
a) Test management
b) Test design
c) Test execution
d) Test planning

25 Which of the following is NOT a white box technique?
a) Statement testing
b) Path testing
c) Data flow testing
d) State transition testing

26 Data flow analysis studies:
a) possible communications bottlenecks in a program.
b) the rate of change of data values as a program executes.
c) the use of data on paths through the code.
d) the intrinsic complexity of the code.

27 In a system designed to work out the tax to be paid:
An employee has £4000 of salary tax free. The next £1500 is taxed at 10%
The next £28000 is taxed at 22%
Any further amount is taxed at 40%
To the nearest whole pound, which of these is a valid Boundary Value Analysis test case?
a) £1500
b) £32001
c) £33501
d) £28000

28 An important benefit of code inspections is that they:
a) enable the code to be tested before the execution environment is ready.
b) can be performed by the person who wrote the code.
c) can be performed by inexperienced staff.
d) are cheap to perform.

29 Which of the following is the best source of Expected Outcomes for User Acceptance Test scripts?
a) Actual results
b) Program specification
c) User requirements
d) System specification

30 What is the main difference between a walkthrough and an inspection?
a) An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.
b) An inspection has a trained leader, whilst a walkthrough has no leader.
c) Authors are not present during inspections, whilst they are during walkthroughs.
d) A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator.

31 Which one of the following describes the major benefit of verification early in the life cycle?
a) It allows the identification of changes in user requirements.
b) It facilitates timely set up of the test environment.
c) It reduces defect multiplication.
d) It allows testers to become involved early in the project.

32 Integration testing in the small:
a) tests the individual components that have been developed.
b) tests interactions between modules or subsystems.
c) only uses components that form part of the live system.
d) tests interfaces to other systems.

33 Static analysis is best described as:
a) the analysis of batch programs.
b) the reviewing of test plans.
c) the analysis of program code.
d) the use of black box testing.

34 Alpha testing is:
a) post-release testing by end user representatives at the developer’s site.
b) the first testing that is performed.
c) pre-release testing by end user representatives at the developer’s site.
d) pre-release testing by end user representatives at their sites.

35 A failure is:
a) found in the software; the result of an error.
b) departure from specified behaviour.
c) an incorrect step, process or data definition in a computer program.
d) a human action that produces an incorrect result.

36 In a system designed to work out the tax to be paid:
An employee has £4000 of salary tax free. The next £1500 is taxed at 10%
The next £28000 is taxed at 22%
Any further amount is taxed at 40%
Which of these groups of numbers would fall into the same equivalence class?
a) £4800; £14000; £28000
b) £5200; £5500; £28000
c) £28001; £32000; £35000
d) £5800; £28000; £32000

37 The most important thing about early test design is that it:
a) makes test preparation easier.
b) means inspections are not required.
c) can prevent fault multiplication.
d) will find all faults.

38 Which of the following statements about reviews is true?
a) Reviews cannot be performed on user requirements specifications.
b) Reviews are the least effective way of testing code.
c) Reviews are unlikely to find faults in test plans.
d) Reviews should be performed on specifications, code, and test plans.

39 Test cases are designed during:
a) test recording.
b) test planning.
c) test configuration.
d) test specification.

40 A configuration management system would NOT normally provide:
a) linkage of customer requirements to version numbers.
b) facilities to compare test results with expected results.
c) the precise differences in versions of software component source code.
d) restricted access to the source code library.
-
#ISTQB #ISTQBDUMPS #ISEB #SOFTWARETESTING
-
https://iseb-software-testing.blogspot.com/2012/09/exam-paper-3-iseb-foundation-software.html

Post has attachment
ISTQB Dumps, Exam Paper 9, ISEB ISTQB Foundation Software Testing

Deciding How much testing is enough should take into account :-

i. Level of Risk including Technical and Business product and project risk
ii. Project constraints such as time and budget
iii. Size of Testing Team
iv. Size of the Development Team

a) i,ii,iii are true and iv is false
b) i,,iv are true and ii is false
c) i,ii are true and iii,iv are false x
d) ii,iii,iv are true and i is false

2. Test planning has which of the following major tasks?

i. Determining the scope and risks, and identifying the objectives of testing.
ii. Determining the test approach (techniques, test items, coverage, identifying and interfacing the teams involved in testing , testware)
iii. Reviewing the Test Basis (such as requirements, architecture, design, interface)
iv. Determining the exit criteria.

a) i,ii,iv are true and iii is false x
b) i,,iv are true and ii is false
c) i,ii are true and iii,iv are false
d) ii,iii,iv are true and i is false

3. Evaluating testability of the requirements and system are a part of which phase:-
a) Test Analysis and Design x
b) Test Planning and control
c) Test Implementation and execution
d) Evaluating exit criteria and reporting

4. One of the fields on a form contains a text box which accepts alphabets in lower or upper case.
Identify the invalid Equivalence class value.
a. CLASS
b. cLASS
c. CLass
d. CLa01ss x

5. In a system designed to work out the tax to be paid:

An employee has £4000 of salary tax free. The next £1500 is taxed at 10% The next £28000 is taxed at 22% Any further amount is taxed at 40% Which of these groups of numbers would fall into the same equivalence class?

a) £4800; £14000; £28000
b) £5200; £5500; £28000
c) £28001; £32000; £35000
d) £5800; £28000; £32000 x

6. Which of the following has highest level of independence in which test cases are :

a) Designed by persons who write the software under test
b) Designed by a person from a different section
c) Designed by a person from a different organization x
d) Designed by another person

7. We use the output of the requirement analysis, the requirement specification as the input for writing :-

a) User Acceptance Test Cases x
b) Integration Level Test Cases
c) Unit Level Test Cases

d) Program specifications

8. Validation involves which of the following

i. Helps to check the Quality of the Built Product
ii. Helps to check that we have built the right product.
iii. Helps in developing the product
iv. Monitoring tool wastage and obsoleteness.

a) Options i,ii,iii,iv are true.
b) ii is true and i,iii,iv are false
c) i,ii,iii are true and iv is false x
d) iii is true and i,ii,iv are false.


9. Which of the following uses Impact Analysis most?

a) Component testing
b) Non-functional system testing
c) User acceptance testing
d) Maintenance testing x

-
#ISTQB #ISTQBDUMPS #ISEB #SOFTWARETESTING
-
Software Testing Blog
https://iseb-software-testing.blogspot.com
-
Download ISTQB Dumps-->
http://iseb-software-testing.co.uk

Post has attachment
ISTQB Dumps, Exam Paper 2: ISEB ISTQB Foundation Software Testing

1.Software testing activities should start
a. as soon as the code is written
b. during the design stage
c. when the requirements have been formally documented
d. as soon as possible in the development life cycle

2.Faults found by users are due to:
a. Poor quality software
b. Poor software and poor testing
c. bad luck
d. insufficient time for testing

3.What is the main reason for testing software before releasing it?
a. to show that system will work after release
b. to decide when the software is of sufficient quality to release
c. to find as many bugs as possible before release
d. to give information for a risk based decision about release

4. which of the following statements is not true
a. performance testing can be done during unit testing as well as during the testing of whole system
b. The acceptance test does not necessarily include a regression test
c. Verification activities should not involve testers (reviews, inspections etc)
d. Test environments should be as similar to production environments as possible

5. When reporting faults found to developers, testers should be:
a. as polite, constructive and helpful as possible
b. firm about insisting that a bug is not a “feature” if it should be fixed
c. diplomatic, sensitive to the way they may react to criticism
d. All of the above

6. In which order should tests be run?
a. the most important tests first
b. the most difficult tests first(to allow maximum time for fixing)
c. the easiest tests first(to give initial confidence)
d. the order they are thought of

7. The later in the development life cycle a fault is discovered, the more expensive it is to fix. why?
a. the documentation is poor, so it takes longer to find out what the software is doing.
b. wages are rising
c. the fault has been built into more documentation,code,tests, etc
d. none of the above

8. Which is not true - The black box tester:
a. should be able to understand a functional specification or requirements document
b. should be able to understand the source code.
c. is highly motivated to find faults
d. is creative to find the system’s weaknesses

9. A test design technique is
a. a process for selecting test cases
b. a process for determining expected outputs
c. a way to measure the quality of software
d. a way to measure in a test plan what has to be done

10. Testware(test cases, test dataset)
a. needs configuration management just like requirements, design and code
b. should be newly constructed for each new version of the software
c. is needed only until the software is released into production or use
d. does not need to be documented and commented, as it does not form part of the released
software system

11. An incident logging system
a only records defects
b is of limited value
c is a valuable source of project information during testing if it contains all incidents
d. should be used only by the test team.

12. Increasing the quality of the software, by better development methods, will affect the time needed for testing (the test phases) by:
a. reducing test time
b. no change
c. increasing test time
d. can’t say

13. Coverage measurement
a. is nothing to do with testing
b. is a partial measure of test thoroughness
c. branch coverage should be mandatory for all software
d. can only be applied at unit or module testing, not at system testing

14. When should you stop testing?
a. when time for testing has run out.
b. when all planned tests have been run
c. when the test completion criteria have been met
d. when no faults have been found by the tests run


15. Which of the following is true?
a. Component testing should be black box, system testing should be white box.
b. if u find a lot of bugs in testing, you should not be very confident about the quality of software
c. the fewer bugs you find,the better your testing was
d. the more tests you run, the more bugs you will find.

16. What is the important criterion in deciding what testing technique to use?
a. how well you know a particular technique
b. the objective of the test
c. how appropriate the technique is for testing the application
d. whether there is a tool to support the technique

17. If the pseudocode below were a programming language ,how many tests are required to achieve 100% statement coverage?
1. If x=3 then
2. Display_messageX;
3. If y=2 then
4. Display_messageY;
5. Else
6. Display_messageZ;
7. Else
8. Display_messageZ;

a. 1
b. 2
c. 3
d. 4

18. Using the same code example as question 17,how many tests are required to achieve 100% branch/decision coverage?

a. 1
b. 2
c. 3
d. 4

19 Which of the following is NOT a type of non-functional test?
a. State-Transition
b. Usability
c. Performance
d. Security

20. Which of the following tools would you use to detect a memory leak?
a. State analysis
b. Coverage analysis
c. Dynamic analysis
d. Memory analysis

21. Which of the following is NOT a standard related to testing?
a. IEEE829
b. IEEE610
c. BS7925-1
d. BS7925-2

22.which of the following is the component test standard?
a. IEEE 829
b. IEEE 610
c. BS7925-1
d. BS7925-2

23 which of the following statements are true?
a. Faults in program specifications are the most expensive to fix.
b. Faults in code are the most expensive to fix.
c. Faults in requirements are the most expensive to fix
d. Faults in designs are the most expensive to fix.

24. Which of the following is not the integration strategy?
a. Design based
b. Big-bang
c. Bottom-up
d. Top-down

25. Which of the following is a black box design technique?
a. statement testing
b. equivalence partitioning
c. error- guessing
d. usability testing

26. A program with high cyclometic complexity is almost likely to be:
a. Large
b. Small
c. Difficult to write
d. Difficult to test

27. Which of the following is a static test?
a. code inspection
b. coverage analysis
c. usability assessment
d. installation test

28. Which of the following is the odd one out?
a. white box
b. glass box
c. structural
d. functional

29. A program validates a numeric field as follows:
values less than 10 are rejected, values between 10 and 21 are accepted, values greater than or equal to 22 are rejected

which of the following input values cover all of the equivalence partitions?
a. 10,11,21
b. 3,20,21
c. 3,10,22
d. 10,21,22

30. Using the same specifications as question 29, which of the following covers the MOST boundary values?
-
#ISTQB #ISTQBDUMPS #ISEB #SOFTWARETESTING
-
https://iseb-software-testing.blogspot.com/2012/09/exam-paper-2-iseb-foundation-software.html

Post has attachment
ISTQB Dumps, Exam Paper 1: ISEB ISTQB Foundation Software Testing
1 When what is visible to end-users is a deviation from the specific or expected behavior, this is called:

a) an error
b) a fault
c) a failure
d) a defect
e) a mistake

2 Regression testing should be performed:
v) every week
w) after the software has changed
x) as often as possible
y) when the environment has changed
z) when the project manager says

a) v & w are true, x – z are false
b) w, x & y are true, v & z are false
c) w & y are true, v, x & z are false
d) w is true, v, x y and z are false
e) all of the above are true

3 IEEE 829 test plan documentation standard contains all of the following except:
a) test items
b) test deliverables
c) test tasks
d) test environment
e) test specification

4 Testing should be stopped when:
a) all the planned tests have been run
b) time has run out
c) all faults have been fixed correctly
d) both a) and c)
e) it depends on the risks for the system being tested

5 Order numbers on a stock control system can range between 10000 and 99999 inclusive. Which of the following inputs might be a result of designing tests for only valid equivalence classes and valid boundaries:
a) 1000, 5000, 99999
b) 9999, 50000, 100000
c) 10000, 50000, 99999
d) 10000, 99999
e) 9999, 10000, 50000, 99999, 10000

6 Consider the following statements about early test design:
i. early test design can prevent fault multiplication
ii. faults found during early test design are more expensive to fix
iii. early test design can find faults
iv. early test design can cause changes to the requirements
v. early test design takes more effort

a) i, iii & iv are true. Ii & v are false
b) iii is true, I, ii, iv & v are false
c) iii & iv are true. i, ii & v are false
d) i, iii, iv & v are true, ii us false
e) i & iii are true, ii, iv & v are false

7 Non-functional system testing includes:
a) testing to see where the system does not function properly
b) testing quality attributes of the system including performance and usability
c) testing a system feature using only the software required for that action
d) testing a system feature using only the software required for that function
e) testing for functions that should not exist

8 Which of the following is NOT part of configuration management:
a) status accounting of configuration items
b) auditing conformance to ISO9001
c) identification of test versions
d) record of changes to documentation over time
e) controlled library access

9 Which of the following is the main purpose of the integration strategy for integration testing in the small?
a) to ensure that all of the small modules are tested adequately
b) to ensure that the system interfaces to other systems and networks
c) to specify which modules to combine when and how many at once
d) to ensure that the integration testing can be performed by a small team
e) to specify how the software should be divided into modules

10 What is the purpose of test completion criteria in a test plan:
a) to know when a specific test has finished its execution
b) to ensure that the test case specification is complete
c) to set the criteria used in generating test inputs
d) to know when test planning is complete
e) to plan when to stop testing

11 Consider the following statements
i. an incident may be closed without being fixed
ii. incidents may not be raised against documentation
iii. the final stage of incident tracking is fixing
iv. the incident record does not include information on test environments
v. incidents should be raised when someone other than the author of the software performs the test

a) ii and v are true, I, iii and iv are false
b) i and v are true, ii, iii and iv are false
c) i, iv and v are true, ii and iii are false
d) i and ii are true, iii, iv and v are false
e) i is true, ii, iii, iv and v are false

12 Given the following code, which is true about the minimum number of test cases required for full statement and branch coverage:
Read P
Read Q
IF P+Q > 100 THEN
Print “Large”
ENDIF
If P > 50 THEN
Print “P Large”
ENDIF

a) 1 test for statement coverage, 3 for branch coverage
b) 1 test for statement coverage, 2 for branch coverage
c) 1 test for statement coverage, 1 for branch coverage
d) 2 tests for statement coverage, 3 for branch coverage
e) 2 tests for statement coverage, 2 for branch coverage

13 Given the following:
Switch PC on
Start “outlook”
IF outlook appears THEN
Send an email
Close outlook

a) 1 test for statement coverage, 1 for branch coverage
b) 1 test for statement coverage, 2 for branch coverage
c) 1 test for statement coverage. 3 for branch coverage
d) 2 tests for statement coverage, 2 for branch coverage
e) 2 tests for statement coverage, 3 for branch coverage

14 Given the following code, which is true:
IF A > B THEN
C = A – B
ELSE
C = A + B
ENDIF
Read D
IF C = D Then
Print “Error”
ENDIF

a) 1 test for statement coverage, 3 for branch coverage
b) 2 tests for statement coverage, 2 for branch coverage
c) 2 tests for statement coverage. 3 for branch coverage
d) 3 tests for statement coverage, 3 for branch coverage
e) 3 tests for statement coverage, 2 for branch coverage

15 Consider the following:
Pick up and read the newspaper
Look at what is on television
If there is a program that you are interested in watching then switch the the television on and watch the program
Otherwise
Continue reading the newspaper
If there is a crossword in the newspaper then try and complete the crossword

a) SC = 1 and DC = 1
b) SC = 1 and DC = 2
c) SC = 1 and DC = 3
d) SC = 2 and DC = 2
e) SC = 2 and DC = 3

16 The place to start if you want a (new) test tool is:
a) Attend a tool exhibition
b) Invite a vendor to give a demo
c) Analyse your needs and requirements
d) Find out what your budget would be for the tool
e) Search the internet

17 When a new testing tool is purchased, it should be used first by:
a) A small team to establish the best way to use the tool
b) Everyone who may eventually have some use for the tool
c) The independent testing team
d) The managers to see what projects it should be used in
e) The vendor contractor to write the initial scripts

18 What can static analysis NOT find?
a) The use of a variable before it has been defined
b) Unreachable (“dead”) code
c) Whether the value stored in a variable is correct
d) The re-definition of a variable before it has been used
e) Array bound violations

19 Which of the following is NOT a black box technique:
a) Equivalence partitioning
b) State transition testing
c) LCSAJ
d) Syntax testing
e) Boundary value analysis



20 Beta testing is:
a) Performed by customers at their own site
b) Performed by customers at their software developer’s site
c) Performed by an independent test team
d) Useful to test bespoke software
e) Performed as early as possible in the lifecycle

21 Given the following types of tool, which tools would typically be used by developers and which by an independent test team:
i. static analysis
ii. performance testing
iii. test management
iv. dynamic analysis
v. test running
vi. test data preparation

a) developers would typically use i, iv and vi; test team ii, iii and v
b) developers would typically use i and iv; test team ii, iii, v and vi
c) developers would typically use i, ii, iii and iv; test team v and vi
d) developers would typically use ii, iv and vi; test team I, ii and v
e) developers would typically use i, iii, iv and v; test team ii and vi

22 The main focus of acceptance testing is:
a) finding faults in the system
b) ensuring that the system is acceptable to all users
c) testing the system with other systems
d) testing for a business perspective
e) testing by an independent test team

23 Which of the following statements about the component testing standard is false:
a) black box design techniques all have an associated measurement technique
b) white box design techniques all have an associated measurement technique
c) cyclomatic complexity is not a test measurement technique
d) black box measurement techniques all have an associated test design technique
e) white box measurement techniques all have an associated test design technique

24 Which of the following statements is NOT true:
a) inspection is the most formal review process
b) inspections should be led by a trained leader
c) managers can perform inspections on management documents
d) inspection is appropriate even when there are no written documents
e) inspection compares documents with predecessor (source) documents

25 A typical commercial test execution tool would be able to perform all of the following EXCEPT:
a) generating expected outputs
b) replaying inputs according to a programmed script
c) comparison of expected outcomes with actual outcomes
d) recording test inputs
e) reading test values from a data file

26 The difference between re-testing and regression testing is
a) re-testing is running a test again; regression testing looks for unexpected side effects
b) re-testing looks for unexpected side effects; regression testing is repeating those tests
c) re-testing is done after faults are fixed; regression testing is done earlier
d) re-testing uses different environments, regression testing uses the same environment
e) re-testing is done by developers, regression testing is done by independent testers

27 Expected results are:
a) only important in system testing
b) only used in component testing
c) never specified in advance
d) most useful when specified in advance
e) derived from the code

28 Test managers should not:
a) report on deviations from the project plan
b) sign the system off for release
c) re-allocate resource to meet original plans
d) raise incidents on faults that they have found
e) provide information for risk analysis and quality improvement

29 Unreachable code would best be found using:
a) code reviews
b) code inspections
c) a coverage tool
d) a test management tool
e) a static analysis tool

30 A tool that supports traceability, recording of incidents or scheduling of tests is called:
a) a dynamic analysis tool
b) a test execution tool
c) a debugging tool
d) a test management tool
e) a configuration management tool

31 What information need not be included in a test incident report:
a) how to fix the fault
b) how to reproduce the fault
c) test environment details
d) severity, priority
e) the actual and expected outcomes

32 Which expression best matches the following characteristics or review processes:
1. led by author
2. undocumented
3. no management participation
4. led by a trained moderator or leader
5. uses entry exit criteria

s) inspection
t) peer review
u) informal review
v) walkthrough

a) s = 4, t = 3, u = 2 and 5, v = 1
b) s = 4 and 5, t = 3, u = 2, v = 1
c) s = 1 and 5, t = 3, u = 2, v = 4
d) s = 5, t = 4, u = 3, v = 1 and 2
e) s = 4 and 5, t = 1, u = 2, v = 3

33 Which of the following is NOT part of system testing:
a) business process-based testing
b) performance, load and stress testing
c) requirements-based testing
d) usability testing
e) top-down integration testing

34 What statement about expected outcomes is FALSE:
a) expected outcomes are defined by the software’s behaviour
b) expected outcomes are derived from a specification, not from the code
c) expected outcomes include outputs to a screen and changes to files and databases
d) expected outcomes should be predicted before a test is run
e) expected outcomes may include timing constraints such as response times

35 The standard that gives definitions of testing terms is:
a) ISO/IEC 12207
b) BS7925-1
c) BS7925-2
d) ANSI/IEEE 829
e) ANSI/IEEE 729

36 The cost of fixing a fault:
a) Is not important
b) Increases as we move the product towards live use
c) Decreases as we move the product towards live use
d) Is more expensive if found in requirements than functional design
e) Can never be determined

37 Which of the following is NOT included in the Test Plan document of the Test Documentation Standard:
a) Test items (i.e. software versions)
b) What is not to be tested
c) Test environments
d) Quality plans
e) Schedules and deadlines

38 Could reviews or inspections be considered part of testing:
a) No, because they apply to development documentation
b) No, because they are normally applied before testing
c) No, because they do not apply to the test documentation
d) Yes, because both help detect faults and improve quality
e) Yes, because testing includes all non-constructive activities

39 Which of the following is not part of performance testing:
a) Measuring response time
b) Measuring transaction rates
c) Recovery testing
d) Simulating many users
e) Generating many transactions

40 Error guessing is best used
a) As the first approach to deriving test cases
b) After more formal techniques have been applied
c) By inexperienced testers
d) After the system has gone live
e) Only by end users
-
#ISTQB #ISTQBDUMPS #ISEB #SOFTWARETESTING
-
https://iseb-software-testing.blogspot.com/2012/09/exam-paper-1-iseb-foundation-software.html

I am a ISTQB certified Software tester, ask me for help if required

Post has attachment
What Is a Test Plan?

A test plan refers to a document that describes the scope, resource, schedule and approach of the projected testing activities.

The test plan identifies the test items, features that need to be tester, the tasks that need to be carried out, the designated person who would perform each of these tasks as well as any risks that may be require contingency planning. In terms of software testing, test plans provide detailed information about the forthcoming testing efforts.

These include: 
The scope of testing
-Test Schedule
-Test Deliverables
-Contingencies and Risks
-Release Criteria

Test plan can also be considered to be the detailed document describing how the process of testing would proceed, who would perform the testing, what are the things that would be tested, how much time it would require to complete the testing process and the quality level to which the testing would be performed. Due to its importance, it is a frequently asked testing interview question in most IT related job interviews.

Creating Test Plans

In the earliest phases of deployment planning, it is the job of the testing team to develop a test plan. This plan defines the scope and objective of all testing efforts as well as identifies the tools, software and hardware that are required for performing the testing. It also specifies the functions and features that would be tested during the process. An all-inclusive test plan also contains information about any potential risk factors that may jeopardize the process of testing.

In case the testing team has been divided into several technology sub-teams, then each of the sub-teams would be responsible for developing a test plan for the specific technology area pertaining to that particular team. For instance, the networking team is required to prepare a test plan related to the testing networking features. Each member of the respective sub-team must review and approve the test plan of that particular team before it can be integrated into the main test plan.

Types of Test Plan

There are a variety of different types of test plans. These include:

Master Test Plan: This is a unified advanced test plan that brings together all the test plans for any particular project / product.

Test Plans for Specific Testing Levels: There are different test plans for each of the levels of the testing process. These include:

-Unit Testing Plan
-System Testing Plan
-Integration Testing Plan
-Acceptance Testing Plan

Test Plans for Specific Testing Types: There are a variety of test plans for the major kinds of testing such as Security Test Plan and Performance Test Plan.

Template for Test Plan

The content and format of any test plan varies greatly depending on the standards, processes as well as test management tools that are being used in the process of testing.

#ISEB #ISTQB #SoftwareTesting #QualityAssurance #QA #Testing #Tester #Selenium #SoftwareDevelopment  #TestPlan   #TestTemplate     #TestPlanExecution   #TestSchedule   #TestScope   #TestDeliverables  
-
ISEB / ISTQB Study Guide: http://iseb-software-testing.co.uk
Photo

Post has attachment
How to write a System Test Plan?

 Imagine for a moment you've just finished a web application for a client. Swimming around within that application is 100 bugs. What proportion of those bugs would you say is acceptable for the client to find (e.g. 50, 30, 10)? The point is, those bugs are going to be found by someone, and its either going to be you or the client. You can think of it as a sliding scale, the more bugs the client finds, the more your creditability suffers and the more damage you do to the business relationship.

In the martial arts there's a saying; "expect the best, but prepare for the worst". The US Navy Seals have a slightly more gun-ho version which goes; "The more you sweat in training, the less you bleed in battle." Notice how it says the ‘less' you bleed in battle, implying that if you enter into combat, you are going to get bloody. Software development is like this too, if you're going to create software, you are going to get bugs.

As a rough guide, you want to try catch at least 80% of all bugs. Ideally, you would go for 100%, a worthwhile but lofty goal. Your best bet for catching as many bugs as possible is to create a system test plan. Creating a decent system test plan is easier said then done. A good place to start is your functional specification (assuming you have one). In effect, your specification gets converted into the system test plan. What you are doing is checking to see if the things you said you were going to do have actually been done.

A test plan is nothing new, in fact, the structure I use was developed by Microsoft years ago. It's a simple format, a test case has a title, some steps, and an expected result. 

I write my test plans with the intent of having an independent QA tester run through it, so no prior knowledge of the system should be assumed. You want someone who has never used the system before because they will take a fresh approach. You're counting on them to use it in a manner which was never intended (e.g. on the ‘My Profile' page, they type in a really long name for the ‘Company' field and crash the system because the database only has room for a 32 character string).

You should keep your test cases short, to the point, and self contained (i.e. they generally don't link to other test cases). If you have a test case that goes over a page, consider breaking it into smaller units. The document itself should be self contained as well, that is; it shouldn't require the QA tester to get up and ask programmers questions like "what's the login password?"

Instruct your QA tester to log any bugs they find in your bug tracking system and also to write a proper description rather then just saying "Test Case 16 failed." You may want to read my article on Logging Bugs Like a Pro for some suggestions on good bug logging practices.


#ISEB #ISTQB #SoftwareTesting #QualityAssurance #QA #Testing #Tester #Selenium #SoftwareDevelopment   #TestPlan   #TestTemplate    #TestCase   #SystemTestPlan  
--
ISEB / ISTQB Study Guide: http://iseb-software-testing.co.uk
Photo

Post has attachment

Top 6 Software Testing Methods

Whitebox testing:
This kind of testing checks the developed structure and the continuous flow of the software. Each code and is checked in the testing helping generate strong and efficient software.      

Blackbox testing:
This testing main intention is to specifically check the Software functionality, this processing ignores the software programming structure.

Performance testing:
This testing does the part of checking the load time and usability in terms of performance of the software.

Unit testing:
This kind of testing is performed by programmers who keep themselves updated with the latest technology. They check the internal codes and the design structure of the specific software.

Automated Testing:
This kind of testing is performed by QA testers. Latest tools and techniques are implemented under controlled condition. QA Services strategies plans for individual deleted bug software and define a goal on how to be enable to deliver you risk free product.

Acceptability Testing:
This is the final test that ensures each product has gone through the detailed testing platform and matches the results asked by the Client.

--
#ISEB #ISTQB #SoftwareTesting #QualityAssurance #QA #Testing #Tester #Selenium #SoftwareDevelopment     #BlackBoxTesting   #WhiteBoxTesting   #AcceptanceTesting   #UnitTesting   #PerformanceTesting   #AutomatedTesting   #TestingMethods  
-
ISEB / ISTQB Study Guide: http://iseb-software-testing.co.uk
Photo
Wait while more posts are being loaded