cucumber / cucumber/messages

Agree conformancy / shape of testStepFinished for each status

Open
#181 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
41
Forks
24
Avg merge
2d 4h
Merged PRs (30d)
6

Description

### 🤔 What's the problem you're trying to solve?

Agree conformancy for `testStepFinished` message for each status enum

### ✨ What's your proposed solution?

Below is a status table for each status and keys that are currently returned

|STATUS|Ruby|JVM|JS|
|-----|-----|-----|----|
|PASSED|status, duration|...|...|
|UNKNOWN|...|...|...|
|PENDING|...|...|...|
|UNDEFINED|status, duration|...|...|
|SKIPPED|status, duration|...|...|
|AMBIGUOUS|...|...|...|
|FAILED|status, duration, message (exception to be added)|...|...|

### ⛏ Have you considered any alternatives or workarounds?

Contributor guide

Open the contributing guide

Research direction

Begin with the testStepFinished status table in the issue and compare the returned keys across Ruby, JVM, and JS. The issue is done when participants agree on a conformant shape for every listed status and clarify the exception handling for FAILED.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, javascript, ruby
Domain
api, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.