Pass the iSQI ISTQB Foundation Level CTFL-AcT Questions and answers with CertsForce

Depending on the model used to simulate the workload, performance tests are called load, stress or endurance / stability tests.

Performance testing aims to determine a system’s robustness against malicious attacks.

The performance of the system is measured in a context that reflects, as far as possible, representative operating conditions.

The performance test results serve to determine hardware and software performance requirements.

GIVEN ii)

WHEN i)

THEN vi)

GIVEN ii)

WHEN iv)

THEN v)

GIVEN iii)

WHEN ii)

THEN iv)

GIVEN ii)

WHEN v) AND vi) THEN i)

Users are qualified depending on their physical and intellectual characteristics.

Use cases are analyzed and represented through business process models.

External conditions are considered as input for subsequent design steps.

Inspirations from similar sectors are sought to identify successful solutions.

Efficiency

Usability

Compatibility

Portability

ii, v and vi

ii, v and vii

i, ii and vi

iii, iv and v

Keeping all model element in one diagram considerably improves the readability of BMPN models.

BPMN diagrams and DMN tables should include information such as traceability to user stories.

Links to requirements or risks should be well separated from the workflow description.

Business analysts should finalize their process models before showing them to acceptance testers.

Vague or ambiguous requirements may lead to misunderstandings both during implementation and testing.

In Agile development lifecycle models, requirement engineering becomes less important due to the product owner role.

INVEST is a technique that ensure the quality of user stories or requirements, thus replacing regular reviews.

Testers may complete unclear requirements by assumptions, as long as they discuss those assumptions with at least one stakeholder.

You invite the team members and ask them to design their own (team-wise) emblem representing their values, beliefs, goals, tasks together than a common motto.

You invite every member in turn to describe his/her past experience and his/her major achievements in the organization or in their former job.

You ask every member in turn to write down three things he/she likes and dislikes in the organization and to post them on a wall. A volunteer is then chosen to read randomly some posts that are then discussed with the group.

You draw a staircase with 11 steps, each of them representing a major milestone of the project. The bottom of the stairs corresponds to the first day of the project and the upper step means that the project is released. You locate the present situation in the top of the stairs. The team is asked to identify and discuss the major steps downwards.

Identify the requirements / user stories that are not satisfied.

Assess the impact of corrective actions on other parts of the system's implementation.

Analyze the function that failed step by step to identify the cause of the defect.

Check, whether other paths in the business process model perform as intended.

In a model-based testing approach, acceptance tests are generated from graphical or textual models.

In a priority-based testing approach, prioritization of acceptance tests depends on identified product risks.

In a risk-based testing approach, acceptance criteria are derived from the tester’s experience and intuition.

In a black-box testing approach, acceptance test scenarios follow the implemented sequence of function calls in the code.