High Level Guideline

[reboottime]

Overview

What to test

Be pragmatic ! Prioritize testing based on user and business needs.

Major Concepts

• 3 A: Arrange -> Action -> Assert
• Choose Proper Test Level: e2e testing -> integration testing -> unit testing
• TDD : Test Driven Development

[reboottime]

Test Case Organization

Guidelines for a single test case

• Principles

  • 3 A: Arrange, Act, Assert
  • Be specific
    • on test case description.
    • on test case topic: single test purpose for a single test case

• Good Example

import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
import '@testing-library/jest-dom';

import Fetch from './fetch';

test('loads and displays greeting', async () => {
  // ARRANGE
  render(<Fetch url="/greeting" />);

  // ACT
  await userEvent.click(screen.getByText('Load Greeting'));
  await screen.findByRole('heading');

  // ASSERT
  expect(screen.getByRole('heading')).toHaveTextContent('hello there');
  expect(screen.getByRole('button')).toBeDisabled();
});

(reference: quick start using react testing library)

Group related test cases using describe

[reboottime]

E2E Test Strategy

1. Identify critical user flows:

   • Determine the most important user journeys and functionalities of your application.
   • Focus on high-priority scenarios that cover the core features and have the greatest impact on user experience.

2. Define test scenarios:

   • Break down each user flow into specific test scenarios.
   • Consider different user roles, inputs, and expected outcomes for each scenario.
   • Include both positive and negative test cases to ensure comprehensive coverage.

3. Prioritize test cases:

   • Assign priority to each test case based on its criticality and potential impact.
   • High-priority test cases should cover the most essential functionalities and critical paths.
   • Lower-priority test cases can be added incrementally as time and resources allow.

4. Design test data:

   • Identify the test data required for each test scenario.
   • Consider different data combinations, edge cases, and boundary values.

5. Develop readable and maintainable tests:

   • Write tests using a clear and consistent structure and naming convention.
   • Use page object pattern or other abstractions to separate test logic from the implementation details.
   • Ensure tests are modular, reusable, and easy to understand and maintain.

6. Handle test environment and data setup:

   • Define a reliable and reproducible test environment setup process.
   • Consider using containerization or virtualization technologies for consistent test environments.
   • Ensure test data is set up and cleaned up properly before and after each test run.

7. Incorporate error handling and reporting:

   • Implement robust error handling mechanisms in your tests.
   • Capture and report test failures, errors, and exceptions clearly and accurately.
   • Provide detailed logs and screenshots to aid in troubleshooting and debugging.

( With the help of Claude.ai)

[reboottime]

When to use Snapshot test