Summer Special Limited Time 65% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: exc65

A test status report SHOULD:

A.

Specify the impediments to carrying out the planned test activities in the reporting period and the corresponding solutions put in place to remove them

B.

Be produced as part of test completion activities and report unmitigated product risks to support the decision whether or not to release the product

C.

Always be based on the same template within an organisation, as its structure and contents should not be affected by the audience to which the report is presented.

D.

Specify the lines of communication between testing, other lifecycle activities, and within the organisation that were chosen at the outset of the test project.

Which one of the following statements correctly describes the term 'debugging'?

A.

There is no difference between debugging and testing.

B.

Debugging is a confirmation activity that checks whether fixes resolved defects.

C.

Debugging is the development activity that finds, analyses and fixes defects.

D.

Debugging is of no relevance in Agile development.

During iteration planning, a scrum team uses an estimation technique called planning poker to estimate the effort required to deliver a critical user story. In advance of the estimation session, the team agreed on some ground rules to limit the number of poker rounds and save time.

The team agreed on the following:

1. They will use the following progression for estimation: Extra-small, Small, Medium, Large, Extra-large, and Extra-extra-large.

2. If estimation values differ significantly, the highest score will be used for estimation purposes.

The result of the first round of planning poker:

Team MemberEstimation

BusinessLarge

DevelopmentExtra-extra-large

TestingExtra-extra-large

Which of the following options best represent the team’s next actions?

A.

The fact that all estimations are high indicate that the user story is not well understood or should be broken down into multiple smaller stories.

B.

The pre-agreed rules state that the highest score should be used for estimation, resulting in the user story being categorised as Extra-extra-large.

C.

Since the business representative is likely to have the most informed view of the requirement, the user story is categorised as a Large.

D.

the team discusses the differences in the estimates and repeats the poker round until an agreemet is reached.

Which of the following statements is TRUE?

A.

User acceptance tests are usually automated and aim to verify the acceptance criteria for user stories

B.

Acceptance criteria for user stories can include details on data definitions, for example by describing the format, allowed values, and default values for a data item

C.

Acceptance criteria for user stones should focus on positive scenarios, while negative scenarios should be excluded

D.

Tests derived from acceptance criteria for user stories are not included in any of the four testing quadrants

You are an experienced tester on a project with incomplete requirements and under pressure to deploy.

What type of testing should you do?

A.

Decision-based testing.

B.

Checklist-based testing.

C.

Error guessing.

D.

Exploratory testing.

A requirement specifies that if the total amount of sales (TAS) made during the year by a corporate seller is 300,000€ or more, the bonus that must be paid to the seller is 100% of a certain amount agreed upon at the beginning of the year. The software contains a fault as it implements this requirement with the decision "IF (TAS = 300,000)" instead of "IF (TAS >= 300.000)". The application of the 3-value boundary value analysis to this problem consists of the following three test cases (TAS is an integer variable):

TC1 = 299,999 TC2=300,000 TC=300,001

Which of the following statements is TRUE?

A.

TC1 would highlight the fault

B.

TC2 would highlight the fault

C.

TC3 would highlight the fault

D.

None of the three test cases would highlight the fault.

During which main group of test activity are the following tasks performed?

•Checking test results and logs against specified coverage criteria.

•Assessing the level of component or system quality based on test results and logs.

•Determining whether more tests are needed.

Select the correct answer:

A.

Test planning.

B.

Test analysis.

C.

Test design.

D.

Test monitoring and control.

Consider a given test plan which, among others, contains the following three sections: "Test Scope", "Testing Communication", and "Stakeholders". The features of the test object to be tested and those excluded from the testing represent information that is:

A.

not usually included in a test plan, and therefore in the given test plan it should not be specified neither within the three sections mentioned, nor within the others

B.

usually included in a test plan and, in the given test plan, it is more likely to be specified within "Test Scope" rather than in the other two sections mentioned

C.

usually included in a test plan and, in the given test plan, it is more likely to be specified within "Testing Communication" rather than in the other two sections mentioned

D.

usually included in a test plan and, in the given test plan, it is more likely to be specified within "Stakeholders" rather than in the other two sections mentioned

Which of the following is a test task that usually occurs during test implementation?

A.

Make sure the planned test environment is ready to be delivered

B.

Find, analyze, and remove the causes of the failures highlighted by the tests

C.

Archive the testware for use in future test projects

D.

Gather the metrics that are used to guide the test project

Which of the following statements about traceability is FALSE?

A.

Traceability between test basis items and the test cases designed to cover them, makes it possible to determine which test basis items have been covered by the executed test cases.

B.

Traceability between test basis items and the test cases designed to cover them, enables experience-based test techniques to be applied

C.

Traceability between test basis items and the test cases designed to cover them, enables identification of which test cases will be affected by changes to the test basis items.

D.

Traceability can be established and maintained through all the test documentation for a given test level, such as from test conditions through test cases to test scripts.