smart-testing
smart-testing copied to clipboard
arquillian
We know which tests you want to run.
##### Issue Overview Copy-to-clipboard feature used in our documentation copies several additional empty lines. ##### Expected Behaviour When I click on the first copy-to-clipboard button [here](http://arquillian.org/smart-testing/#_don_t_make_me_think) then copied content should...
##### Issue Overview Currently `TestVerifier` class verifies if a file coming from SCM is a test by checking if it is a java file (ends with `.java`), if so it...
##### Issue Overview Currently, each and every strategy assumes we are using Git and relies on this VSC to detect changes in the project. The goal of this task is...
When no strategy is defined, then the tool should provide/use some default set/order of strategies that will be used. My proposal is: `new,changed,failed`
Currently affected strategy just creates a graph between tests and imports of these tests. Then with any change on a Java class (business class) it checks on the graph which...
Currently all smart testing properties are defining using prefix `smart.testing`. Currently user have to type entire `smart.testing` while applying each property for smart testing. We can change that prefix from...
Enable smart testing to run against [smart testing](https://github.com/arquillian/smart-testing) repository. Currently in smart testing, we are running all tests in surefire parallel mode configuration with `reuseFork=true`. **Issues** - If we enable...
Next to functional tests, we should extend our verification test suite with new approaches letting us discover potential integration problems with build tools as projects use them slightly different (e.g....
Take one (ideally buggy) project and go eg. 100 commits back in its history. Then run the whole test suite: * without ST * with ST in the selecting mode...
As we can now execute `Test Bed` [tests against any repository](https://github.com/arquillian/smart-testing/blob/60ec2978a62b71d80e43da54dcb676a549af046b/functional-tests/test-bed/src/main/java/org/arquillian/smart/testing/ftest/testbed/rules/GitClone.java#L38), we should develop a simple smoke test to see if we can configure our extension against arbitrary projects. The...