-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Improve Best Practice Guide]: Unit testing, et. al. #24
Comments
Maybe we need another ticket for these, but it'd be good to have recommendations / starter kits / tool pointers for:
|
I will focus on covering those in the Reference Architecture first. Maybe we should split this one off from the Starter Kit? |
Yeah - agreed @jpl-jengelke. Reference architecture would help lay the context, but separate starter kits (if it makes sense) would be a good approach. |
+1'd by @ramesh-maddegoda, @nttoole, @galenatjpl, @celskeggs, @sharimayer, @pymonger |
The JUnit tests in the Java-side are already completed, although they may benefit from updates. |
Checked for duplicates
Yes - I've already checked
Best Practice Guide
Continuous Testing
Best Practice Guide Sections
Describe the improvement
We'd like to have starter kits for helping the SLIM community with getting a JUnit or PyUnit testing framework up and running, by providing real world example templates to customize and start using. Additionally, having an architectural reference diagram explaining how Java unit test using JUnit in Jenkins would ideally work would be great. These two were mentioned in previous changelog reports, but were pushed to be done later.
The text was updated successfully, but these errors were encountered: