Question 1

If you are testing a mobile banking application, is it important to test the interaction between the software and the device?

Accepted Answer

B

Explanation: Testing the interaction between a mobile application and the device is critical. The physical device is the primary medium through which the user interacts with the application (via touchscreen, buttons, etc.) and how the application connects to external services, such as the internet for a banking app. This interaction testing validates that the application functions correctly with the device's hardware (e.g., network radios, GPS, camera), operating system, and can handle interruptions (e.g., incoming calls, notifications). For a high-risk application like mobile banking, ensuring this interaction is seamless and reliable is essential for functionality, security, and user trust.

Question 2

You are testing a machine that scores exam papers and assigns grades. Based on the score achieved
the grades are as follows:
1-49 = F, 50-59 = D-, 60-69 = D, 70-79 = C, 80-89 = B, 90-100=A
If you apply boundary value analysis, how many test cases will you need to achieve minimum test
coverage?

Accepted Answer

B

Explanation: Boundary Value Analysis (BVA) is a test design technique that focuses on the values at the edges or boundaries of equivalence partitions. The problem defines six valid partitions for scores (1-49, 50-59, etc.) and two invalid partitions (scores 100). This creates seven distinct boundaries where the system's behavior changes: at the minimum/maximum valid scores (1 and 100) and between each adjacent grade range (e.g., between 49 and 50). Standard two-point BVA requires testing the value on each side of every boundary. The seven boundaries are 0/1, 49/50, 59/60, 69/70, 79/80, 89/90, and 100/101. Each boundary requires two test cases, resulting in a total of 7 2 = 14 test cases.

Question 3

Which of the following is a requirement for portability testing for the future of a mobile application?

Accepted Answer

B

Explanation: Portability testing evaluates an application's ability to function effectively in different environments. For the future of a mobile application, this requires a forward-looking strategy. Testers and stakeholders must analyze market trends to anticipate which devices, operating systems, and form factors will become popular. This foresight is crucial for defining the scope of future portability tests, ensuring the application remains compatible and provides a good user experience as the mobile ecosystem evolves. This strategic anticipation guides the selection of devices and environments for testing, whether real or emulated, to proactively address future compatibility challenges.

Question 4

What types of testing are particularly important for mobile applications based on the user’s expectations?

Accepted Answer

B

Explanation: From a user's perspective, the immediate experience of using a mobile application is paramount. Usability testing ensures the application is intuitive, easy to navigate on various screen sizes, and provides a positive user experience. Performance testing addresses critical user expectations regarding speed, responsiveness, and efficient use of device resources like battery and data. Mobile users have low tolerance for slow, confusing, or resource-intensive applications, making these two non-functional test types particularly important for app adoption and retention. They directly reflect the "how well" an application works in the user's hands.

Question 5

If a tool is able to simulate the way in which a specific device would respond to an application, it is considered to be what type of simulator?

Accepted Answer

B

Explanation: A native device simulator is a software tool designed to mimic the software environment and configurations of a specific mobile device. It allows developers and testers to run and test an application in an environment that behaves like a particular target device (e.g., a specific model of an iPhone or Android phone) without needing the physical hardware. This type of simulator replicates the device's operating system, screen resolution, and standard application programming interfaces (APIs), providing a representation of how the application will respond on that native platform.

Question 6

In lifecycle models, what should testing provide in term of speed of releasing the product to market?

Accepted Answer

D

Explanation: The primary role of testing within any software development lifecycle is to act as a risk management activity. It aims to provide stakeholders with sufficient information to make informed decisions about product release. This involves a pragmatic balance between ensuring quality and meeting business objectives, such as time-to-market. The goal is not to find every possible defect, which is impossible, but to focus test efforts on areas of highest risk. This approach helps prevent catastrophic failures in the live environment while ensuring that the testing process itself does not become an unreasonable bottleneck to the product's release schedule.

Question 7

A mobile device has some peripherals attached to it, if your application uses a peripheral of them to operate, what should you do regarding this peripheral?

Accepted Answer

C

Explanation: A comprehensive test strategy for an application dependent on a peripheral must validate two key scenarios. First, testing with the peripheral ensures the application correctly utilizes the hardware for its intended features (interoperability). Second, testing without the peripheral is crucial for robustness testing. This verifies that the application handles the absence of the hardware gracefully, for instance, by displaying an informative message or disabling the relevant feature, rather than crashing or behaving unpredictably. This approach covers both positive and negative test cases for the dependency.

Question 8

What is a major difference between mobile applications and traditional software?

Accepted Answer

B

Explanation: A major differentiator between mobile and traditional software is user context and expectations. Users of traditional software, particularly in enterprise or professional environments, are often a "captive audience." They may be required to use a specific application for their job and have fewer alternatives, leading to a higher tolerance for performance issues like slowness. In contrast, the mobile application market is characterized by intense competition and low user switching costs. Mobile users have extremely low patience for performance problems and are very likely to uninstall a slow or unresponsive application in favor of a competitor. This difference in user commitment is a critical consideration for mobile development and testing strategies.

Question 9

Tax rates on income are: 0% for up to 5000 EUR, 10% is added for each additional 5000 EUR up to
20,000 EUR, and 40% is applied for above 20,000 EUR, which test inputs in EUR would be selected for
valid equivalence partitions?

Accepted Answer

B

Explanation: Equivalence Partitioning is a black-box test design technique where test cases are designed to exercise representative values from partitions. The tax rules create five distinct valid partitions for income: 1. Up to 5,000 EUR 2. 5,001 to 10,000 EUR 3. 10,001 to 15,000 EUR 4. 15,001 to 20,000 EUR 5. Above 20,000 EUR The principle is to select one test value from within each partition. Option B (3000, 6000, 12000, 19000, 30000) is the only choice that provides a single, representative value from each of these five valid partitions, thus achieving 100% coverage for this technique.

Question 10

You have information from production that the previous version of your product has had a high rate
of abandonment after the initial download. In fact, it appears people download the application and
never use it. Poor performance is thought to be the main problem that is causing people to give up
the application.
Which of the following aspects of the application should be specifically targeted for testing to help
determine if this is really the problem?

Accepted Answer

D

Explanation: The scenario describes users abandoning the application immediately after the initial download and before any meaningful interaction ("never use it"). This points to a failure at the very first step of the user experience. Application launch time is the first performance characteristic a user encounters. An excessively long launch time creates a poor first impression and is a direct and plausible reason for immediate abandonment, thus aligning perfectly with the observed user behavior and the hypothesis that poor performance is the cause. Testing this specific metric is the most targeted way to validate the hypothesis.

Question 11

What is the primary use of teststorming?

Accepted Answer

C

Explanation: Teststorming is a collaborative, experience-based test technique analogous to brainstorming. The primary purpose is for a diverse group of team members (e.g., testers, developers, product owners) to collectively generate test ideas, identify potential risks, and define test scenarios or charters for exploratory testing. It leverages the varied perspectives of the participants to achieve broader and deeper test coverage than an individual might devise alone. The focus is on the creative and systematic derivation of what and how to test, which is then formalized into test cases and scenarios.

Question 12

What does the word OTA mean?

Accepted Answer

B

Explanation: The acronym OTA stands for "Over-the-Air." This term describes the method of distributing software updates, firmware, and configuration data to electronic devices, such as mobile phones, tablets, and IoT devices, through a wireless network (e.g., Wi-Fi, cellular). OTA updates are a fundamental mechanism for deploying new features, applying security patches, and fixing bugs without requiring a physical connection to a computer. In the context of mobile application testing, verifying the OTA update process is a critical test type to ensure the application and device function correctly after an update.

Question 13

You are testing an application that will allow users to scan the bar code from a package mailing label
and then receive emails from the package shipper as the package moves through the various stages
of its delivery (e.g., pickup, receipt at central processing, routing, delivery). If requested, the user can
also receive a picture of the signature of the recipient of the package. This is a web browser-based
application. It is expected that this application will have wide usage across a large set of devices and
networks with varying speeds and reliability.
Your company has several competitors who are working on similar products although your
company’s product has some new innovations and a very attractive user interface. As a result, once it
is released, your company expects to grab that majority market share.
Given this information, what would be the best approach for doing your testing to ensure the
capabilities of the product are tested as well as the range of environments and networks?

Accepted Answer

D

Explanation: A cloud-based virtual test environment is the best approach because it directly addresses the two primary challenges presented: testing across a "large set of devices" and "networks with varying speeds and reliability." These platforms provide on-demand access to a vast library of real mobile devices from various manufacturers, running different OS versions. Crucially, they also offer network virtualization (or simulation) capabilities, allowing testers to mimic real-world network conditions such as low bandwidth, high latency, and packet loss. This combination provides the most comprehensive, scalable, and controlled solution for ensuring both functionality and performance across the expected diverse user environments.

Question 14

As life cycle models adapt to meet the needs of the mobile application market, how will the interaction between the developers and testers change?

Accepted Answer

D

Explanation: The mobile application market demands rapid development cycles and frequent releases, leading to the widespread adoption of Agile and DevOps methodologies. A core principle of these models is the "whole-team approach," where testers are integrated directly into the development team. This contrasts with traditional models where testing was a separate, sequential phase. In modern lifecycles, developers and testers work together continuously from the start, participating in activities like daily stand-ups, backlog grooming, and continuous integration. This tight integration and shared responsibility for quality inherently lead to a significant increase in collaboration between the two roles.

Question 15

Which of the following is most typically a task the tester performs in mobile security testing?

Accepted Answer

B

Explanation: A fundamental and most typical task for a tester in mobile security testing is to verify the security of data at rest. This involves ensuring that sensitive information, such as usernames, passwords, session tokens, and personal user data, is not stored in an unencrypted or otherwise unprotected format within the application's local storage on the device (e.g., in plist files, SQLite databases, or shared preferences). This check is crucial because a compromised device could otherwise lead to a complete compromise of the user's account and data. This task directly addresses one of the most common mobile application vulnerabilities.

Free ASTQB ASTQB Actual Exam Questions