Handshake
Guidelines
Guidelines
  • 👩‍🍳Architecture
    • 🎯Idea
    • 📡Server
  • 🏡Local Setup
    • 🍡Introduction
    • 🏁Requirements
    • 🚂Setup
    • Page
    • 📊Dashboard Setup
      • 🎲Sample Data
      • 📗Storybook Setup
    • 🎵Handshake-Nodejs-Reporters
      • Test Packages
    • 👮CodeQL Local Setup
  • ✈️Pipeline
    • 🎡Workflows
    • 🔌Triggers
Powered by GitBook
On this page
  1. Architecture

Idea

Understanding how handshake works

NextServer

Last updated 12 months ago

The idea is that while your framework runs, we would spawn Handshake Server through their listener, The Server Job is simple, it just needs to store the results in the right tables.

Once Tests are completed, we will run a command to transform the results, we calculate certain outputs for example:

  • Calculate the Broken Suites based on the Assertions Added through their status

  • Link Suites with a previously retried suite

  • Status of the Test Run

  • Number of Indirect Test cases for a suite

  • Generate the JSON for all the stored tables to generate the reports.

Once done, we would move the dashboard build to the desired location and the generated JSON to the static build. once done we can host the folder.

In the rest of the pages, we can rest on how each of these steps is done through modules.

👩‍🍳
🎯
Overview
Drawing