starnowski / bmunit-extension Goto Github PK

Create integration with Travis

Add the junit5-extension submodule which will support integration with JUnit5 library. The module needs to be compiled with Java version 8.

Create an example test with the usage of the Spock framework and native Java mechanisms, just like the example test "UserControllerTest.java" for JUnit4.
All changes should be added to the "article_examples" branch.

Add test for method st.bmunit.extension.BMUnitUtils#joinEnlist(java.lang.Object)

Based on example from https://github.com/codecov/example-java-maven or https://github.com/codecov/example-java

Missing: no javadoc jar found in folder '/com/github/starnowski/bmunit/extension/junit4-rule/1.0.1'
Missing: no javadoc jar found in folder '/com/github/starnowski/bmunit/extension/utils/1.0.1'

[Maven] Update project version from "0.1.0" to "0.2.0-SNAPSHOT"

Create new maven module "junit4-rule-utils-demo".
Move all tests which use of "com.github.starnowski.bmunit.extension:utils" library from "junit4-rule-demo" module to "junit4-rule-utils-demo".
Leave or create new tests in module "junit4-rule-demo" which don't use "com.github.starnowski.bmunit.extension:utils" library.

Create the demo application with users registration functionality

Update Travis configuration file so that commits which contains phrase [TRAVIS_IGNORED_COMMIT] would not be trigger Travis build

Publish the "1.0.1" project version into the GitHub maven repository.
The description of how it could be done can be found on page https://help.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages#authenticating-to-github-packages.

In case if issue is :
* feature - feature/{issue number}{short description}
* bugfix - bugfix/{issue number}{short description}

Add license file

Change project group from "st.bmunit.extension" to "com.github.starnowski.bmunit.extension" based on description from site https://central.sonatype.org/pages/choosing-your-coordinates.html.

Create release branch 1.1.
Deploy release branch 1.1 into the maven repository.
Change the master branch version to 1.2.

Prepare for the article purprose the example code where instead of using the "bmunit-extension" library the native java mechanisms will be used for tests purpose.
For example for test https://github.com/starnowski/bmunit-extension/blob/master/junit4-spock-spring-demo/src/test/java/com/github/starnowski/bmunit/extension/junit4/spock/spring/demo/controllers/UserControllerTest.java
try to use the "java.util.concurrent.CountDownLatch" type just like in example on page https://stackoverflow.com/questions/17827022/how-is-countdownlatch-used-in-java-multithreading

Useful links:
https://developer.jboss.org/message/987411?et=watches.email.thread&_sscc=t#987411

Change project descriptor file so that artifacts were deployed with java files

Update README.md document and mention about demo application with specific examples

Add package info for artifacts "com.github.starnowski.bmunit.extension:junit4-rule" and "com.github.starnowski.bmunit.extension:utils". Package info should contains information about its components and what they are used for.

Add test for method st.bmunit.extension.BMUnitUtils#joinWait(Object, int, long)

• Create project github repository
• Deploy release 0.1.0

Add demo application, similar to "junit4-spock-spring-demo".

Check if the "utils" module is compatible with Byteman in version 4.X. Consider adding a build step that will run a maven with a specific profile. The profile is going to have dependencies for the Byteman library in version 4.X.