Build Pipeline Run with API Testing: A 2027 Project Guide

The starting point for this API Testing exercise is a student DevOps learner working with run records. Their question is specific: What is the average duration of passed runs by pipeline? Building a HTTP contract test suite around that question gives the project a manageable scope and makes the result possible to verify.

This is a 2027 study-edition project brief. All example records and operational situations are fictional. Start with basic API Testing knowledge, the ability to inspect structured data and a local practice environment. The complete first version should answer the stated question before adding accounts, real integrations or additional screens.

Define the project rule

Average passed-run duration excludes failed runs but must be accompanied by their count. Re-running a commit creates a new run identifier, not an overwrite of the previous evidence. For this exercise, one row represents one run. The stable key is record_id; pipeline_name is the grouping or filtering label. The numeric duration_seconds field uses seconds. Accepted states are queued, passed, failed.

The summary selects status passed and applies mean to the selected numeric values. Keep this definition visible in the interface, response or report so another learner can reproduce it. Use positive finite values in the starter fixture and define any future zero or missing-value policy explicitly.

Choose the API Testing approach

Specify the request method, path, permitted fields and response contract. Test both the returned body and the resulting state. A success status alone cannot prove that an operation occurred once or that a rejected request changed nothing. Give each test a controlled setup and inspect retry, duplicate and malformed-input outcomes explicitly.

The three design decisions to explain in your project notes are:

• Request and response contracts. Apply this choice to run records and explain its effect on duration_seconds.
• State assertions after a request. Apply this choice to run records and explain its effect on duration_seconds.
• Isolated fixtures. Apply this choice to run records and explain its effect on duration_seconds.

Work through a small sample

The three records below are deliberately small enough to inspect by hand. They are a compact specification for the data shape and expected result, and can later be expanded into a larger synthetic fixture.

[
  {
    "record_id": "build-pipeline-runs-01",
    "pipeline_name": "Unit Checks",
    "duration_seconds": 25,
    "status": "passed",
    "recorded_on": "2027-01-04"
  },
  {
    "record_id": "build-pipeline-runs-02",
    "pipeline_name": "Package Build",
    "duration_seconds": 40,
    "status": "queued",
    "recorded_on": "2027-01-05"
  },
  {
    "record_id": "build-pipeline-runs-03",
    "pipeline_name": "Preview Verification",
    "duration_seconds": 15,
    "status": "passed",
    "recorded_on": "2027-01-06"
  }
]

Only the first and third records match passed. Their duration_seconds values are 25 and 15; the full-fixture result is 20 seconds, with 2 matching records. Selecting pipeline_name = Unit Checks leaves the first record, so the result becomes 25 seconds, with 1 match. This provides two independent checks for the filter and aggregation.

The full-fixture output contract is:

{
  "matching_count": 2,
  "operation": "mean",
  "value": 20,
  "unit": "seconds"
}

Check the result by pipeline_name

The overall figure answers the all-records version of the question. Grouping by pipeline_name produces the following separate expectations, using the same passed rule. The middle group has a record in the source fixture but no qualifying observation.

Use this breakdown when answering the group-level question. Compare like-for-like units and keep the matching count visible, especially for averages. A different filter changes which records enter the calculation; it does not change the meaning of the metric.

The code blocks describe sample data and an expected result. Implement the surrounding feature using the installed version of your chosen tools, then save the actual run evidence separately from these expectations.

Build the feature in three passes

1. Turn the rule into assertions

Write an observable expectation for passed run records and the mean of duration_seconds. Include the selected pipeline_name and seconds label in the expected result. Define a clean setup so each case starts from known data.

2. Cover a change and a rejected input

Run the supplied scenario-specific acceptance check, then try a missing pipeline_name, an invalid duration_seconds and a repeated identifier. Inspect both the returned response and resulting state. A rejection should explain the correction and preserve valid existing records.

3. Make the evidence reproducible

Record exact inputs, actions, expected outcomes and actual outcomes. Automate checks only at the boundary supported by the chosen tool. Keep fixtures independent and capture useful failure evidence without replacing a precise assertion with a screenshot alone.

Find the mistake before polishing the result

A useful defect to introduce deliberately is: A rerun overwrites the failed run and makes history look clean. First reproduce it against the fixture, then identify the smallest rule or state transition that explains the mismatch. Fix that boundary and rerun the full-fixture and selected-label examples. This creates a stronger explanation than changing several unrelated parts until the screen looks right.

The scenario-specific acceptance check is: Keep separate run identifiers and display the original failed outcome. Preserve before-and-after evidence. Add a missing pipeline_name, a negative duration_seconds, an unrecognised status and a duplicate record_id as separate invalid cases. Define the rejection or duplicate-handling policy before testing, and verify that invalid input does not silently change valid existing records.

Check the API Testing concerns as well:

• Invalid requests must not mutate records.
• A duplicate request needs a defined outcome.
• Response values must reconcile to stored state.

For an empty filter match, the expected mean value is undefined (no matching observations). Keep matching_count at zero. This distinction prevents an empty dataset from being interpreted as a measured observation.

Explain the finished work in a portfolio

Show the student DevOps learner question, the record definition and the expected calculation first. Then demonstrate a pipeline_name filter and the acceptance check. Include the fixture, setup instructions, chosen tool versions, actual test output and one remaining limitation in the repository. If you show a screenshot, pair it with the input that produced it. Another learner should be able to repeat the same result from a clean checkout.

For a focused extension, add a second pipeline_name selection and compare the two groups using the same rule. Specify how missing groups appear and keep the original fixture as a regression case. Expand scope only after the current calculation, state handling and recovery path remain understandable.

Questions learners often ask

Which run records belong in the result?

Select records whose status is exactly passed and that satisfy the chosen pipeline_name filter. Other states remain in the source data and can have separate summaries. Follow the domain rule above when a record changes state.

What should happen when no records match?

Treat the empty result as undefined and show a clear no-observations message. Keep the applied filter visible so the user can change it. Avoid using a loading indicator for a completed request that simply has no matching data.

How can I prove the duration_seconds result is correct?

Reconcile the first and third sample records, then repeat the calculation for Unit Checks alone. Save both expected and actual outputs, and rerun the scenario-specific acceptance check after making a change.

Continue learning with Groot Academy

Use this exercise as a concrete discussion point when choosing a learning path. Browse the current Groot Academy course directory and ask about the current syllabus, learning mode and project practice. Course availability and batch details should be confirmed directly with the academy.

For implementation details, consult the official API Testing documentation matching the tools you install. This project defines an original practice brief; it does not depend on a forecast about 2027 software releases.

Continue with Deployment History using API Testing, or compare Build Pipeline Run using Playwright. These companion practice guides are part of the 2027 learning collection.