Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unit tests exist for each class #99

Open
5 tasks
BradleyBoutcher opened this issue Oct 29, 2020 · 0 comments
Open
5 tasks

Unit tests exist for each class #99

BradleyBoutcher opened this issue Oct 29, 2020 · 0 comments

Comments

@BradleyBoutcher
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently, tests are built for an end-to-end environment. There are four JUnit
tests located within the Java classpath, which require external setup and teardown.

Describe the solution you would like

A unit test is written for each individual method in each class for the Conjur Java API.
This includes:

  • Mocking framework for tests that require complex input
  • JUnit superclass's setUp() and tearDown() methods for shared resources
  • All tests should be runnable "offline", or piecemeal, quickly
  • The existing bin/test.sh script becomes bin/run-integration.sh, and a new script called bin/run-unit.sh is created to easily run the new tests
  • Integration tests (the four currently existing) are moved to their own Class and are only run when specified, rather than part of the standard unit test suite.

Additional context

To run existing tests, run ./bin/test.sh. This will create a Conjur environment and export variables required for the
existing tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant