Autodesk / Autodesk/shore

Allow defining E2E test in Jsonnet

Open
#24 1 comment 0 reactions 0 assignees View on GitHub
Backend-Spinnaker DevX E2E Renderer-JSONNET
Dominant language
Go
Stars
21
Forks
4
PR merge metrics
No merged PRs in 30d

Description

## Summary

Although YAML is a great description language, when a large enough test set is required, things get out of hand.

The CLI tool already support Jsonnet, so it shouldn't be very hard to both support it as a renderer and provide a simple library to define [TDD](https://en.wikipedia.org/wiki/Test-driven_development) (or even [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development)) style definitions for tests.

## Motivation

## Describe alternatives you've considered

## Additional context

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the CLI's existing Jsonnet support and comparing it with how YAML test definitions are handled. The issue does not name files, tests, or an agreed design; done would require a defined Jsonnet renderer and a clear test-definition library scope.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.