test: add requirement(s) in the form of executable BDD scenarios

[rjaegers]

Pull Request

Description of changes

This PR adds support for writing requirements in the form of executable BDD scenarios to amp-devcontainer. At the moment there is only one scenario implemented for a compilation "smoke" test.

Checklist

• I have followed the contribution guidelines for this repository
• I have added tests for new behavior, and have not broken any existing tests
• I have added or updated relevant documentation
• I have verified that all added components are accounted for in the SBOM

[github-actions]

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-rust:latest to ghcr.io/philips-software/amp-devcontainer-rust@sha256:ccc8e72ca9ca9941bbff0ae40c7ce550cd9992407367334099e60bae1e162f1d

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	433.13M	427.23M	-5.90M (-1.36%)
linux/arm64	572.34M	566.66M	-5.68M (-0.99%)

[github-actions]

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:latest to ghcr.io/philips-software/amp-devcontainer-cpp@sha256:aba9339c83403514edc7933411a4f9b0a58352f68304d71bef176a47b70a78c1

OS/Platform	Previous Size	Current Size	Delta
linux/amd64	653.79M	645.82M	-7.98M (-1.22%)
linux/arm64	646.22M	638.39M	-7.83M (-1.21%)

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	16		0	0.08s
✅ DOCKERFILE	hadolint	2		0	0.63s
✅ GHERKIN	gherkin-lint	1		0	0.44s
✅ JSON	npm-package-json-lint	yes		no	0.42s
✅ JSON	prettier	15	2	0	0.64s
✅ JSON	v8r	14		0	30.54s
✅ MARKDOWN	markdownlint	8	0	0	0.94s
✅ MARKDOWN	markdown-table-formatter	8	0	0	0.22s
✅ REPOSITORY	checkov	yes		no	14.4s
✅ REPOSITORY	gitleaks	yes		no	0.28s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	grype	yes		no	13.65s
✅ REPOSITORY	secretlint	yes		no	1.11s
✅ REPOSITORY	syft	yes		no	0.41s
✅ REPOSITORY	trivy	yes		no	5.89s
✅ REPOSITORY	trivy-sbom	yes		no	0.96s
✅ REPOSITORY	trufflehog	yes		no	2.62s
✅ SPELL	lychee	54		0	1.88s
✅ YAML	prettier	21	0	0	1.0s
✅ YAML	v8r	21		0	15.76s
✅ YAML	yamllint	21		0	0.39s

See detailed report in MegaLinter reports

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

• oxsecurity/megalinter/flavors/[email protected] (61 linters)
• oxsecurity/megalinter/flavors/[email protected] (70 linters)

MegaLinter is graciously provided by

[github-actions]

Test Results

 2 files  ±0   2 suites  ±0   51s ⏱️ -1s
26 tests ±0  26 ✅ ±0  0 💤 ±0  0 ❌ ±0 
28 runs  ±0  28 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 0b4af04. ± Comparison against base commit 04e2fcf.

♻️ This comment has been updated with latest results.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Pull Request Report (#557)

Static measures

Description	Value
Number of added lines	777
Number of deleted lines	62
Number of changed files	17
Number of commits	13
Number of reviews	2
Number of comments (w/o review comments)	5
Number of reviews that contains a comment to resolve	1
Number of reviews that requested a change from the author	0
Number of reviews that approved the Pull Request	1
Get the total number of participants of a Pull Request	4

Time related measures

Description	Value
PR lead time (from creation to close of PR)	23 Days
Time that was spend on the branch before the PR was created	47.2 Min
Time that was spend on the branch before the PR was merged	23 Days
Time to merge after last review	3.1 Hours

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	18.4 Min
Total time spend in last status check run on PR	18.1 Hours