What are some common heuristics for testing web applications?

1 The HICCUPPS heuristic

One of the most popular heuristics for testing web applications is the HICCUPPS heuristic, which stands for History, Image, Comparable Products, Claims, User Expectations, Product, Purpose, and Standards. This heuristic helps you compare the behavior of the web application with different sources of consistency and identify potential inconsistencies that might indicate a bug. For example, you can check if the web application matches its previous versions (History), its branding and design (Image), its competitors or alternatives (Comparable Products), its documentation or marketing (Claims), its intended users' needs and preferences (User Expectations), its own features and functions (Product), its intended goals and outcomes (Purpose), and its legal or technical requirements (Standards).

2 The SFDPOT heuristic

Another useful heuristic for testing web applications is the SFDPOT heuristic, which stands for Structure, Function, Data, Platform, Operations, and Time. This heuristic helps you analyze the different aspects of the web application and generate test ideas based on them. For example, you can explore how the web application is built and organized (Structure), what it does and how it does it (Function), what kind of data it uses and produces (Data), what kind of devices and browsers it supports and interacts with (Platform), how it is deployed and maintained (Operations), and how it behaves over time and under different conditions (Time).

3 The FEW HICCUPS heuristic

A third heuristic for testing web applications is the FEW HICCUPS heuristic, which stands for Familiarity, Emotions, Worldview, History, Image, Culture, Complexity, Uniqueness, Plurality, and Sensitivity. This heuristic helps you consider the different perspectives and experiences of the users and stakeholders of the web application and identify potential issues that might affect their satisfaction and trust. For example, you can test how the web application meets the users' level of knowledge and comfort (Familiarity), how it evokes positive or negative feelings (Emotions), how it aligns with the users' values and beliefs (Worldview), how it reflects the users' past interactions and memories (History), how it presents itself and its identity (Image), how it adapts to the users' cultural and social norms (Culture), how it handles the users' cognitive load and attention span (Complexity), how it differentiates itself from other web applications (Uniqueness), how it supports the users' diversity and inclusion (Plurality), and how it respects the users' privacy and security (Sensitivity).

4 The Mnemonics for Testing Heuristics

The heuristics we have discussed are not the only ones you can use for testing web applications. There are many other heuristics that can help you test different aspects of the web application, such as usability, accessibility, performance, security, reliability, etc. You can find some of these heuristics in the form of mnemonics, which are easy to remember words or phrases that represent a set of concepts or criteria. For example, you can use the CRUSSPIC STMPL mnemonic to test the usability of the web application, which stands for Consistency, Recognition, Understandability, Simplicity, Stability, Politeness, Information Scent, Control, Satisfaction, Support, Personalization, Identity, Context, Speed, Testability, Memorability, Privacy, and Learnability.

5 The Heuristic Test Strategy Model

The heuristics we have discussed can also be combined and organized into a heuristic test strategy model, which is a framework that helps you plan and execute your testing activities based on your context and goals. The heuristic test strategy model consists of four main elements: project environment, product elements, quality criteria, and test techniques. The project environment includes the factors that influence your testing approach, such as stakeholders, resources, schedule, risks, etc. The product elements include the components and features of the web application that you want to test. The quality criteria include the standards and expectations that you want to evaluate the web application against. The test techniques include the methods and tools that you want to use to perform the testing. By using the heuristics as inputs for each element, you can create a comprehensive and flexible test strategy that suits your needs.

6 The Exploratory Testing Dynamics

The heuristics we have discussed can also be used as part of the exploratory testing dynamics, which are the actions and interactions that you perform during your testing sessions. The exploratory testing dynamics include four main activities: learning, designing, executing, and reporting. Learning involves gathering information and understanding the web application and its context. Designing involves creating test ideas and scenarios based on your learning and heuristics. Executing involves performing the tests and observing the results. Reporting involves communicating your findings and feedback to the relevant stakeholders. By using the heuristics as guides and triggers for each activity, you can enhance your testing skills and deliver valuable insights.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?