Video summary

Cómo Escribir Casos de Pruebas | Paso a paso

Main summary

Key takeaways

Educational

Main Ideas / Concepts

  • Testing fundamentals: The video revisits what test cases are and how to use them effectively.
  • Reference standard (ISO/IEC 29119):
    • Defines test case as a set of:
      • preconditions
      • inputs
      • expected results
      • used to execute a test item to achieve test objectives such as:
        • correct implementation
        • error identification
        • quality checking
        • additional valuable information
    • Defines a test case specification document as: a collection of one or more test cases.
    • Recommends that for each test case you include:
      • unique identifier
      • objective
      • priority
      • traceability (often managed via a separate artifact like a traceability matrix)
    • Recommends including fields such as:
      • preconditions
      • inputs
      • expected results
      • actual results (real outcomes after execution)
  • Practical focus: Designing and writing test cases using an example from a Human Resources management system.
  • Test design principle shown: Even with a partial UI rule (only Name is required), test cases should account for what happens when:
    • required fields are missing
    • only required fields are filled
    • optional fields are filled
    • the user cancels the creation flow
    • the unit is added under different levels/locations in the organization tree

Example System Scenario

  • System feature being tested: Adding a unit in the organization structure.
  • Navigation/path in the app:
    • Admin > Organization > Structure
  • How the action works (as described):
    • Click Edit
    • Use the green plus to add units
    • A form opens with fields:
      • Unit number
      • Name
      • Description
    • Only rule clearly enforced: Name is required
    • It suggests the system likely accepts any character (not restricted to numbers/letters/special characters based on observation).

Methodology / Test Case Structure Presented (Detailed)

When writing each test case, the video recommends including (based on ISO/IEC 29119 and practical experience):

  • Unique identifier (ID)
  • Objective
  • Priority
  • Traceability
    • can be maintained in a test case traceability matrix
  • Preconditions (state that must be true before executing)
  • Inputs (data used in the test)
  • Expected results (what should happen)
  • Actual results (what actually happened after running the test)
  • Outcome/status handling:
    • Open / Closed (or Passed / Failed depending on organization)

List of Test Cases Designed for “Add a Unit to Organization Structure”

In the exercise, the creator designs six test cases for adding a unit:

  1. Test Case One: Add a unit with all fields left empty
  2. Second test case: Add a unit with only the required field left empty
    • (Subtitles are inconsistent, but intent is missing required-field coverage.)
  3. Third test case: Add a unit by filling only the required field
    • Example outcome mentioned: it saves the unit named “account”
  4. Fourth test case: Add a unit by filling all fields
  5. Fifth test case: Fill all fields, then cancel
    • Expected to verify that the unit is not created
  6. Sixth test case: Create/add a unit under the appropriate structure, including consideration of adding to a lower-level node
    • Subtitles indicate the created unit ends up under “orange” (as observed in the UI after the action)

The speaker also invites viewers to suggest any missing test cases in the comments.

Completed Test Case (Test Case One) — Fully Outlined

Test Case One: Add a Unit with All Fields Empty

  • Identifier / Name: “Test Case One”

Preconditions

  • The base unit / node required to add new structures must already exist.
  • Specifically, you may delete other nodes, but at least the main node must remain to allow adding further units.

Inputs

  • The data of the new unit (as described for the example fields):
    • address (mentioned in subtitles)
    • name and description (implied: leaving them empty for this test)

Steps to Execute

  1. Enter username and password
  2. Authenticate as system administrator (PSE is referenced)
  3. Go to Admin > Organization > Structure
  4. Click Edit
  5. Click the plus symbol under the unit where you want the new unit
  6. Click Save without filling any fields

Expected Results

  • Clicking Save with no entries shows a message stating that the Name field is required
  • The Name field should be highlighted

Postconditions / Verification

  • Even though “Save” was clicked, the existing units remain unchanged
  • The unit is not added because required fields were left empty

Test Case Status

  • Open
  • Status can be Open/Closed or Passed/Failed, depending on the organization and priority settings

Priority Considerations

  • Priority can be high / medium / low (as noted)

Speakers / Sources Featured

  • Video creator / instructor (primary speaker; name not provided in subtitles)
  • ISO/IEC 29119 standard (referenced as the conceptual basis for test case definitions and documentation)
  • YouTube channel/community prompts:
    • “Testing and Club Group” (Facebook group mentioned)

Original video