Skip to content
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.

Releases: redhat-best-practices-for-k8s/test-network-function

v1.0.8 Improve config error handling

30 Apr 16:10
600a5f7
Compare
Choose a tag to compare

This release fixes a bug with error handling around loading configuration files that was masking real errors.

Fix containerized offering

29 Apr 19:08
Compare
Choose a tag to compare
Bump version to v1.0.7

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Fix docker image

29 Apr 18:23
Compare
Choose a tag to compare
version bump to v1.0.6

ssssss-off-by: Ryan Goulding <rgouldin@redhat.com>

Initial release of containerized solution

03 Mar 22:32
Compare
Choose a tag to compare
Release containerized solution

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Bug fixes and minor improvements.

02 Mar 21:14
Compare
Choose a tag to compare
Version bump for release

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Improve test offering documentation

22 Feb 18:30
Compare
Choose a tag to compare
Version bump for release

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Improved Branch Naming and makefile usability

18 Jan 19:44
Compare
Choose a tag to compare
Improve branching vernacular

Fixes some remanents left over from renaming the default branch to "main".

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Initial CNF Certification Release

16 Dec 21:14
Compare
Choose a tag to compare

CNF Certification 1.0 is the first public release of CNF Certification. It delivers a test suite, comprising a test framework and an initial set of tests, via an upstream git repository. A primary goal of the test framework is to enable test development to keep pace with OpenShift releases. Specifically, being able to develop and add new tests in a timely fashion as each new OpenShift release becomes available is essential.

First version which outputs a claim

10 Nov 16:11
Compare
Choose a tag to compare
Pre-release
Populate claim data

This patch populates all claim data except for lshw characteristics, which is
tracked separately by CTONET-528.  This fulfills the definition of done
requirements for CTONET-580.

In order to make this change, some heavier architectural decisions were made.
First, it was made explicit (in CONTRIBUTING.md) that configuration must be
provided with working MarshalJSON and UnmarshalJSON interfaces (whether they
are purely inherited or custom if needed).  The reason is a claim is defined
using JSON, and to make the test session repeatable, the configuration must be
included in the claim.

To keep track of the different configurations available, a lightweight
singleton pool is abstracted called `Pool`.  Different configurations must
register with the Pool so they are included in the Claim.  Information for
registering with the Pool is included in Contributing.md.

Version information is currently in pre-release, but eventually should be
populated by a build system.  For now, a "version.json" was abstracted to allow
developers to bump the version, so it may be included in the claim file.  Simply
rev the version with a commit, then tag a release.

Changes were 100% unit tested.  The generated claim.json file was tested for
compliance with test-network-function-claim's claim-schema.json (v0.0.4).

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>