Skip to main content

GUI and Usability Test Scenarios

1. All fields on a page (e.g. text box, radio options, drop-down lists) should be aligned properly.
2. Numeric values should be justified correctly unless specified otherwise.
3. Enough space should be provided between field labels, columns, rows, error messages etc.
4. The scrollbar should be enabled only when necessary.
5. Font size, style, and colour for headline, description text, labels, infield data, and grid info should be standard as specified in SRS.
6. Description text box should be multi-lined.
7. Disabled fields should be greyed out and users should not be able to set focus on these fields.
8. Upon click of an input text field, mouse arrow pointer should get changed to the cursor.
9. The user should not be able to type in drop down select lists.
10. Information filled by users should remain intact when there is an error message on page submit. The user should be able to submit the form again by correcting the errors.
11. Check if proper field labels are used in error messages.
12. Drop-down field values should be displayed in defined sort order.
13. Tab and Shift+Tab order should work properly.
14. Default radio options should be pre-selected on the page load.
15. Field-specific and page level help messages should be available.
16. Check if the correct fields are highlighted in case of errors.
17. Check if the drop-down list options are readable and not truncated due to field size limit.
18. All buttons on a page should be accessible by keyboard shortcuts and the user should be able to perform all operations using a keyboard.
19. Check all pages for broken images.
20. Check all pages for broken links.
21. All pages should have a title.
22. Confirmation messages should be displayed before performing any update or delete operation.
23. Hourglass should be displayed when the application is busy.
24. Page text should be left justified.
25. The user should be able to select only one radio option and any combination for checkboxes.

Comments

Post a Comment

Popular posts from this blog

Introduction to Apache JMeter

Apache JMeter is a great open source application with awesome testing abilities. Web Server is a platform which carries loads of numbers of applications and users, so that it is necessary to know that how does it works or performs means; how effective it is to handle simultaneous users or applications. For example; how the “Gmail” supporting server will perform when numbers of users simultaneous access the Gmail account – basically have to do performance testing using performance testing tools like JMeter, Loadrunner etc. To check the high performance of the application or server, do high performance testing using JMeter for exceptional results. Before understanding Overview of JMeter , let us have a look on three testing approach, Performance Test : This test provides the best possible performance of the system or application under a given configuration of infrastructure. Very fast, it also highlights the change need to be made before application goes into prod...
Post a Comment
Read more

Why Agentic AI is the Future of Functional Testing

A gentic AI (AI agents with autonomy and reasoning ability) is rapidly transforming software testing, especially functional testing . Let’s break it down clearly: 🧠 What Is Agentic AI? Agentic AI refers to autonomous AI systems that can: Understand goals (e.g., “verify all checkout flows work”) Plan and reason about how to achieve them Take actions like navigating UIs, generating test cases, or running automation scripts Adapt based on feedback or changing application states Unlike traditional AI (which performs fixed predictions or classifications), agentic AI can act , learn , and self-improve over time. ⚙️ Why It’s the Future of Functional Testing 1. Self-Generating and Self-Maintaining Tests Traditional automation struggles with maintenance — UI changes break scripts constantly. Agentic AI solves this by: Observing the app’s UI, flows, and APIs Generating relevant test cases automatically Adapting scripts when elements change (e.g., detecting a new but...
Post a Comment
Read more

Software Testing Documents

Software Testing Documents- I) Test Policy (Company Level Document) 1) Test Definition              (Verification & Validation) 2) Testing Process (Proper planning before starts testing) 3) Testing Standards 4) Testing Measurements (QAM, TTM, PCM) 5) Risks 6) Approvals 7) Comments 8) Revision History -------------------------------------------------------- II) Test Strategy (Company Level Document) Table of Contents 1.0    Introduction 2.0    Objective 3.0    Scope of the Document 4.0    Test Approach 4.1              Introduction 4.2              Functional and Usability Issues 5.0        Phases of Testing 5.1        ...
Post a Comment
Read more