ISTQB Certified Tester Foundation Level. Курс для початківців. Практика з тестами для 1 розділу.

Ціна помилки чи дефекту

Перш ніж почати розгляд тестів. Варто зазначити кілька моментів, які можуть допомогти у виявленні правильної відповіді на тест.

Чим раніше буде знайдено помилку, тим менші наслідки це матиме для проєкту і тим легше таку помилку буде виправити.

І ще один момент. Чим раніше виявляється помилка чи дефект, тим дешевше їх виправити.

Якість ПЗ

Якість ПЗ – ступінь, в якій система, компонент або процес задовольняють потреби або очікування замовника або користувача.

Функціональність (Functionality) – визначається здатністю ПЗ вирішувати завдання, які відповідають зафіксованим і очікуваним потребам користувача, за заданих умов використання ПЗ. Тобто ця характеристика відповідає за те, що ПЗ працює справно і точно, функціонально сумісно, відповідає стандартам галузі та захищене від несанкціонованого доступу.

Надійність (Reliability) – здатність ПЗ виконувати необхідні завдання у зазначених умовах протягом заданого проміжку часу або вказаної кількості операцій. Атрибути даної характеристики – це завершеність і цілісність всієї системи, здатність самостійно і коректно відновлюватися після збоїв у роботі, відмовостійкість.

Зручність використання (Usability) – можливість легкого розуміння, вивчення, використання і привабливість ПЗ для користувача.

Ефективність (Efficiency) – здатність ПЗ забезпечувати необхідний рівень продуктивності згідно з виділеними ресурсами, часом та іншими зазначеними умовами.

Зручність супроводу (Maintainability) – легкість, з якою ПЗ може аналізуватися, тестуватися, змінюватися для виправлення дефектів, для реалізації нових вимог, для полегшення подальшого обслуговування та адаптуватися до наявного оточення.

Портативність (Portability) – характеризує ПЗ з точки зору легкості його перенесення з одного оточення (software/hardware) в інше.

Варто зазначити, що зараз є і діє серія стандартів ISO 25000, в якій міститься новий підхід до якості. Зокрема збільшення характеристик і виділення “підрівнів” чи додаткових характеристик якості. Тим не менше цей підхід вважається трохи ускладненим, тому для початківців часто дають саме попередню версію ISO 9126. Яка простіша для розуміння і вивчення якої полегшить процес ознайомлення з новою концепцією серії стандартів 25000.

Розбір тестових питань по першому розділу

В цьому відео робиться спроба розібрати кілька десятків питань по першому розділу сілабусу ISTQB CTFL.

Всі питання з відео з правильними відповідями наводяться нижче.

Question 1

Which of the following is most important to promote and maintain good relationships between testers and developers?

1. Understanding what managers value about testing.
2. Explaining test results in a neutral fashion.
3. Identifying potential customer work-arounds for bugs.
4. Promoting better quality software at any cost.

Question 2

Which is not a testing principle

1. Early testing.
2. Pesticide paradox.
3. Exhaustive testing.
4. Defect clustering.

Question 3

According to the ISTQB Glossary, a risk relates to which of the following?

1. Negative consequences that could occur.
2. Negative consequences that will occur.
3. Negative feedback to the tester.
4. Negative consequences for the test object.

Question 4

According to the ISTQB Glossary, the word ‘bug’ is synonymous with which of the following words?

1. Defect
2. Mistake
3. Error
4. Incident

Question 5

A test team consistently find between 90% and 95% of the defects present in the system under test. While the test manager understands that this is a good defect-detection percentage for her test team and industry, senior management and executives remain disappointed in the test group, saying that the test team misses too many bugs. Given that the users are generally happy with the system and that the failures which have occurred have generally been low impact, which of the following testing principles is most likely to help the test manager explain to these managers and executives why some defects are likely to be missed?

1. Absence-of-errors fallacy
2. Exhaustive testing is impossible
3. Defect clustering
4. Pesticide paradox

Question 6

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.

1. i,ii,iv are true and ii is false.
2. i,ii,iii are true and iv is false.
3. i,ii are true and iii,iv are false.
4. ii,iii,iv are true and i is false.

Question 7

Typically, exit criteria may consist of:

1. Defining the amount, level of detail structure, and templates for the test documentation.
2. Estimates of defect density or reliability measures.
3. Adequacy of the test approaches taken.
4. Discussions on disaster recovery.

Question 8

Detecting a defect at which of the following stage is most economical?

1. Build.
2. Deployment.
3. Testing.
4. Design.

Question 9

During which test activity could faults be found most cost effecftively?

1. Execution.
2. Design.
3. Check Exit criteria completion.
4. Planning.

Question 10

Ensuring that test design starts during the requirements definition phase is important to enable which of the following test objectives?

1. Finding defects through dynamic testing.
2. Preventing defects in the system.
3. Finishing the project on time.
4. Gaining confidence in the system.

Question 11

What factors should be considered to determine whether enough testing has been performed? I. The exit criteria. II. The budget. III. How big the test team is. IV. The product’s risk profile. V. How good the testing tools are. VI. Sufficient details of the system status to allow decisions

1. i and ii and iv and vi
2. i and ii and iii and vi
3. ii and iii and iv and v
4. i and ii and v and vi

Question 12

Evaluating testability of the requirements and system are a part of which phase?

1. Test Implementation and execution.
2. Test Analysis and Design.
3. Evaluating exit criteria and reporting.
4. Test Planning and control.

Question 13

Test Implementation and execution has which of the following major tasks? I. Developing and prioritizing test cases, creating test data, writing test procedures and optionally preparing the test harnesses and writing automated test scripts. II. Creating the test suite from the test cases for efficient test execution. III. Verifying that the test environment has been set up correctly. IV. Determining the exit criteria.

1. I,II are true and III, IV are false
2. I,IV,III are true and II is false
3. II,III,IV are true and I is false
4. I,II,III are true and IV is false

Question 14

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.

1. I,III,IV are true and II is false.
2. I,II,IV are true and III is false.
3. I,II are true and III,IV are false.
4. II,III,IV are true and I is false.

Question 15

Which of the following are ‘Exit Criteria’?

1. Acceptance criteria, completion criteria, pass/fail criteria.
2. Coverage of code, schedule, estimates of defect density.
3. The last executable statement within a component.
4. Cost overruns.

Question 16

Testing Process comprised of

1. Test Plan and Test Cases.
2. Test Log and Test Status.
3. Defect Tracking.
4. All of the above.

Question 17

Which of the following are valid test objectives? I. Finding defects. II. Gaining confidence about the level of quality and providing information. III. Preventing defects. IV. Debugging the code.

1. i, ii and iii
2. i, ii and iv
3. ii and iii
4. i and iv

Question 18

The goal of software testing is to

1. Validate that the system behaves as expected.
2. Let the developer know the defects injected by him.
3. Execute the program with the intent of finding errors.
4. Debug the system.

Question 19

Though activities in the Fundamental test process may overlap or occur concurrently, identify the logical sequential process. (i) Test Implementation and Execution (ii) Test Closure activities (iii) Evaluating exit criteria and reporting (iv) Test Planning and Control (v) Test Analysis and Design

1. v – i – iii – ii – iv
2. iv – v – iii – ii – i
3. iv – v – i – iii – ii
4. v – ii – iii – i – iv

Question 20

What is not the primary data given by the tester in test execution?

1. Number of test executed to date.
2. Number of test cases written for change request.
3. Total number of tests.
4. Number of tests executed successfully to date.

Question 21

What is the need for test planning?

1. to understand testing process.
2. to perform ad hoc testing.
3. to utilize a balance of testing techniques.
4. to collect metrics.

Question 22

Which of the following test organizations has the highest level of independence?

1. Independent testers within the development teams
2. Independent testers from the user community
3. Independent test specialists for specific test types, such as usability, performance or certification test specialists
4. Code tested by another developer from the development team

Question 23

What is the USUAL sequence for performing the following activities during the Fundamental Test Process? (a) Analyze the test basis documents. (b) Define the expected results. (c) Create the test execution schedule. (d) Establish the traceability of the test conditions

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

Question 24

What should be taken into account to determine when to stop testing? I Technical risk; II Business risk; III Project constraints; IV Product documentation

1. I, II, and IV are true; III is false
2. I and II are true. III and IV are false
3. I, II, and III are true, IV is false.
4. III is true, I, II, and IV are false

Question 25

When should you stop testing?

1. when the test completion criteria have been met.
2. when no faults have been found by the tests run.
3. when all planned tests have been run.
4. when time for testing has run out.

Question 26

When what is visible to end-users is an imperfection in a work product where it does not meet its requirements, this is called:

1. An error.
2. A defect.
3. A fault.
4. A mistake.

Question 27

Which activities form part of test planning? (i) Developing test cases. (ii) Defining the overall approach to testing. (iii) Assigning resources. (iv) Building the test environment. (v) Writing test conditions.

1. iv& v are true, i, ii & iii are false.
2. i, ii &iv are true, iii & v are false.
3. i, ii & iii are true iv& v are false.
4. ii & iii are true, i, iv& v are false.

Question 28

It is recommended to perform exhaustive tests for covering all combinations of inputs and preconditions

1. Yes, it’s strongly recommended.
2. No, risk analysis and priorities should be used to focus testing efforts
3. Yes, and it’s also necessary to include all the exit combinations
4. Only the expert testers can make exhaustive tests.

Question 29

Which of the following is a major task of test planning?

1. Preparing test specifications.
2. Evaluating exit criteria and reporting.
3. Determining the test approach.
4. Measuring and analyzing results.