Explore the core differences between functional and non-functional testing in mobile app development. This quiz helps users identify test types, objectives, and common scenarios using clear, example-based questions on mobile application quality assurance.
Which aspect does functional testing primarily assess in a mobile app?
Explanation: Functional testing focuses on verifying that each function of the app operates according to the requirements. Speed of loading and battery usage are considered non-functional aspects, not functional ones. The presence of graphical effects relates more to user interface design than to functional validation.
Which test is an example of non-functional testing in a mobile application?
Explanation: Non-functional testing covers app behaviors such as performance, reliability, or scalability. Verifying logins, signups, and notification delivery are functional tests as they check if specific features work. Only performance under load checks a non-functional aspect.
Is usability testing considered a functional or non-functional test in mobile app testing?
Explanation: Usability testing measures how easy and satisfying it is for users to interact with an app, which is a non-functional aspect. It doesn't verify if a specific function works, but rather how users experience the app. Structural and security are distinct types of testing, unrelated to basic usability.
A tester checks if a mobile app can handle 10,000 simultaneous users. What type of testing is this?
Explanation: Testing for the ability to handle a large number of users is non-functional, as it deals with performance and scalability. Functional testing would focus on what the app does, not how well it does it under stress. Integration testing checks component interactions, and syntax testing is unrelated to app performance.
What is the primary goal of functional testing in mobile application development?
Explanation: Functional testing aims to verify that every functional requirement of the app is met and works right. Data usage, screen brightness, and app size are all non-functional characteristics, not checked by functional tests.
Which of the following best describes the main objective of non-functional testing?
Explanation: Non-functional testing is about checking qualities such as reliability, performance, and security aspects. Verifying button functions, business logic, and validation rules are examples of functional testing, not non-functional.
Security testing in mobile apps, such as checking for unauthorized data access, falls under which category?
Explanation: Security testing is a type of non-functional testing, as it examines how well the app protects against threats. Alpha testing is about early-stage user feedback, unit testing checks small code parts, and functional testing does not typically include security checks.
A developer wants to verify that a mobile app responds well to various screen sizes and orientations. What kind of testing is this?
Explanation: Testing responsiveness across different devices deals with usability and adaptability, both considered non-functional. Functional tests focus on what features do, not how they appear or adapt. Syntax and regression testing refer to code correctness and unintended changes, not UI responsiveness.
When a tester checks if an app refuses to accept letters in a numeric field, which testing type is this?
Explanation: Ensuring data fields accept valid input follows the functional requirements and is functional testing. Non-functional testing doesn't verify input rules. Explorative and beta testing have different scopes and do not fit specifically here.
Which test is most likely to be considered functional rather than non-functional?
Explanation: Verifying password reset functionality checks a specific feature, making it a functional test. Measuring startup time, monitoring memory use, and evaluating crash rates all relate to non-functional performance and stability.