Managing tests through the feature life cycle

Open
#805 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading issue #803 and this issue's discussion about moving the propertyDependencies tests. The thread needs a decision between moving tests at the experimentation or stable stage, or introducing a release/stage filter flag; done means the project has an agreed test-lifecycle policy.

Written by the indexing model from the issue text.

Description

Sorry, I missed the discussion on #803 about moving the propertyDependencies tests to a new directory. I don't disagree with that move, but I realize that it isn't clear when these tests should be moved into the main suite. I think it should be when the feature reaches the "experimentation" phase because that's when we expect implementations to start implementing the keyword, but I imagine some of you are thinking it would be when the features moves to the "stable" stage. I want people's builds to break when a feature gets to the point where they should be implementing it. It's one way we can nudge implementers about new features. I just wanted to make sure we're on the same page on this.

This may be a bit of a tangent, but as an alternative, I was thinking about introducing a flag on tests that says what release or stage a test requires. Then people can easily filter out tests they want to ignore and we don't have to worry about separate directories for proposal tests.

Pinging @gregsdennis and @karenetheridge specifically for your thoughts.

Dominant language
Python
Stars
750
Forks
307
Avg merge
3d 17h
Merged PRs (30d)
24

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from json-schema-org/JSON-Schema-Test-Suite

All issues in json-schema-org/JSON-Schema-Test-Suite

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.