human side of software testing? what do you mean? Well... in the basis a human is always "the software tester". But companies want to check fast for certain functionalities being okay and there comes automation into the picture. Automated checking. However false positives and such lay on the lure... so whatever a PC states, PASS / Not Okay... there's always need for a human to do the actual verification. Whether it's a test tool an a.i. or even...a future thing, the principle stays the same. an interesting Youtube.

Different layers, what do you mean? If your energy company is down and a whole city block is without power. Does your System Under Test work? Well yeah maybe if you have a generator but in general 'no' If the battery of your laptop is empty, can you test? If the hardware that your System Under Test needs is not functioning, can you test? And so on and so forth.... layers

• Unit, Integration, E2E
• or
• Unit, Integration, Component, E2E

• Priority: High, Medium and Low
• and also
• Severity: High, Medium and Low?

Severity = Impact on the system or users if the requirement is not implemented (e.g., critical vs. nice-to-have).
Severity describes the consequence or damage caused by omission or failure, not the business ordering.

Priority = The order in which the business wants the requirement to be addressed (e.g., “we need this for release X”).
Priority reflects stakeholder scheduling, deadlines and business value.

Use both — and keep their terms distinct.
Suggested severity scale (examples): Critical / Major / Minor / Cosmetic.
Suggested priority scale (examples): P0 (release-blocker) / P1 (high — next sprint) / P2 (medium) / P3 (low/backlog).

Rule of thumb: Never reuse the same labels for both fields. Severity = impact; Priority = business order.

This also means in Scrum refinements: A Acceptance Criteria can be : Requirment1 and Requirement2 have to be fullfilled. Requirement1 : Input field 3 of page 2 may only contain alphanumeric testcase1: B testcase2: 7 testcase3: & Requirement1 = High Requirement2 = Medium This information must be stated in the UserStory! Definition of Done: there is a link between the check in the test automation and the requirement(s) in the UserStory!

// cypress/e2e/dummy.cy.js
// Target: https://softwaretestingbreak.com/testapplication-web.php

import driveCar from '../helpers/Drivehelper'
import driveCarRandom from '../helpers/DrivehelperRandom'

/**
 * FEATURE-LEVEL TAGS: beschrijven het hele testblok
 * @ui: user interface test
 * @feature:drive-car: functionaliteit “Drive Car”
 */
describe(
    'UI Basic Test – Drive Car',
    {
        tags: ['@ui', '@feature:drive-car']
    },
    () => {

        /**
         * REQUIREMENT: REQ-201
         * PRIORITY: High
         * TESTCASE: TC-201-1
         */
        it(
            'TC-201-1: Drive car and check success message',
            {
                tags: [
                    '@high',
                    '@requirement:REQ-201',
                    '@testcase:TC-201-1'
                ]
            },
            () => {
                cy.visit('https://softwaretestingbreak.com/testapplication-web.php')
                driveCar(1, 1, 1)

                // OrangeBeard attributes
                cy.orangeBeardAttributes({
                    Requirement: 'REQ-201',
                    Testcase: 'TC-201-1',
                    Priority: 'High',
                    Feature: 'Drive Car'
                })

                cy.contains(
                    'Hey nice! not a b_ug, but you found the API call!',
                    { timeout: 7000 }
                ).should('be.visible')
            }
        )
  ...