Timeline for Run impacted tests right after code change
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2014 at 6:39 | answer | added | Fosna | timeline score: 1 | |
| Jun 16, 2014 at 7:36 | comment | added | Fosna | @Yash "Continuous Integration" is not the answer I was looking for. Thank you for trying to help. Guess question is not good enough. | |
| Jun 16, 2014 at 7:34 | comment | added | Fosna | @SayusiAndo Thx. It's close. I remembered I've seen screencast on the main page showcasing near real time test execution and red or green icons on each line showing pass or fail test results. | |
| Jun 13, 2014 at 22:26 | history | tweeted | twitter.com/#!/StackSQA/status/477577741496094720 | ||
| Jun 11, 2014 at 13:37 | answer | added | Peter M. - stands for Monica | timeline score: 0 | |
| Jun 11, 2014 at 12:28 | comment | added | Yash | One option is going the "Continuous Integration" way. You can have your tests executed as soon as a build is created. But it's not selective, as you mentioned is what you are looking for. | |
| Jun 11, 2014 at 11:16 | review | First posts | |||
| Jun 11, 2014 at 15:54 | |||||
| Jun 11, 2014 at 11:13 | comment | added | AndrasCsanyi | It sound's very interesting. I was wondering how beneficial would be use such a tool. I've found this searching for the keywords you mentioned: Parasoft Stuff. | |
| Jun 11, 2014 at 10:56 | history | asked | Fosna | CC BY-SA 3.0 |