Skip to content

Releases: servicebinding/conformance

v0.3.2

12 Oct 16:10
e3b7a69
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.3.1...v0.3.2

v0.3.1

12 Jun 23:33
Compare
Choose a tag to compare

Resolved a race condition found in parallel tests.

What's Changed

  • Make 'provisioned-secret' unqiuely named by @scothis in #59

Full Changelog: v0.3.0...v0.3.1

v0.3.0

24 May 19:45
ce7ae57
Compare
Choose a tag to compare

What's Changed

  • Bump requests from 2.28.2 to 2.31.0 in /features by @dependabot in #55
  • Bump alpine from 3.17.3 to 3.18.0 in /resources/apps/generic-test-app by @dependabot in #54
  • ci: use kind as a test cluster by @sadlerap in #56
  • Use behavex as a test runner by @sadlerap in #57
  • Bump behavex from 1.6.0 to 2.0.1 in /features by @dependabot in #58

Full Changelog: v0.2.1...v0.3.0

v0.2.1

25 Apr 19:03
593aa76
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.2.0...v0.2.1

v0.2.0

08 Dec 20:51
9c55d8d
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.1.0...v0.2.0

v0.1.0

19 Oct 22:07
05a444f
Compare
Choose a tag to compare

0.1.0 🎉

This is the first v0.1.0 release of the conformance test suite.

Dependencies

To run conformance tests, you'll need a python 3 installation and a kubernetes environment available via kubectl.

Running the test suite

First, obtain a copy of this repository and run setup.sh to set up testing dependencies. This only needs to be done once.

Once dependencies have been set up, use the provided run_tests.sh script to run conformance tests.

Conformance status

This does not test conformance of all aspects of the specification. Currently implemented are tests for the following:

  • Binding tests for provisioned services
  • Binding tests for direct secret injection.