Skip to content

Commit

Permalink
WiP Scenario Development Process Basics
Browse files Browse the repository at this point in the history
  • Loading branch information
jspetrak committed Sep 3, 2024
1 parent 72767fe commit 383b152
Show file tree
Hide file tree
Showing 2 changed files with 33 additions and 0 deletions.
6 changes: 6 additions & 0 deletions developer-guide.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,9 @@
---
layout: page
title: Developer Guide
permalink: /developer-guide/
---

# Developer Guide

To develop new test scenarios, developer must have experience with the Postman application, basic proficiency in Javascript language and understand concepts of the OSDM specification itself as the structures and functions used to build the request and validate the result are mostly identical with objects from OSDM.
Expand Down
27 changes: 27 additions & 0 deletions process.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
layout: page
title: Scenario Development Process
permalink: /development-process/
---

# Scenario Development Process

Scenarios used for testing and validation of OSDM APIs can be developed by the members of OTST, or third parties. The development process ensures every scenario to be agreed, specified, documented, and tested against live APIs.

The process is managed using [Github Issues](https://github.com/UnionInternationalCheminsdeFer/OSDM-testing/issues) and [Github Project](https://github.com/orgs/UnionInternationalCheminsdeFer/projects/11).

Everyone can suggest new scenario by creating an _Issue_ at Github. Every scenario suggestion must contain brief description of what should be tested, if there are particular requirements on `Trip` (single/multi-leg, mono/multi-modal, etc.), products (NRT, TLT, IRT, reservations, ancillaries, etc.), number of passengers or others.

Issue status:

* **Open**: Unsorted list of scenario suggestions or other tasks to reviewed
* **Specification**: Issues agreed by OTST to be developed. For scenarios, formal SFR Document is created at [Github Wiki](https://github.com/UnionInternationalCheminsdeFer/OSDM-testing/wiki) and `Scenario Type Prefix` is assigned.
* **Design**: Issues that have formal description of expected functionality or change. For scenarios, formal SSD Document is created at Github Wiki.
* **In progress**: Development of the changes or functionality described in the issues, SFR and SSD.
* **In review**: Code review of developed changes.
* **In testing**: Functional testing of developed changes.
* **Done**: Issue has been completed.

**SFR** - Scenario Functional Requirements

**SSD** - Scenarion Solution Description

0 comments on commit 383b152

Please sign in to comment.