version control - Are there any tools for viewing a "pass/fail" history of unit tests with respect to SCM commits? -

It seems as if there is no nucleus that I'm almost sure something like this should exist . I do not know where to find it. On the other hand, there are probably technical reasons, it is impossible, and I am not seeing them.

But basically, I think that if it is a special unit test, one can test a history (such as with the help of a CI server), in which the red / green position of the test in question Affects. So, I want to see a history like this for Unit Text X; I can see a history that looks like this:

  modification | Date | Test X Status ------------------------------------- 123 | 2011-03-20 | Unsuccessful 120 2011-03-19 | Passed 119 | 2011-03-19 | Failed 112 | 2011-03-16 | Passed 111 | 2011-03-16 | Pending   
 Hope this makes sense: What I want to see will basically be a filtered list of the committee, only for those people who have a specific unit in question Have some effect (X).  
 Does such a device exist ( anywhere  â ??, as a standalone tool, as a component of some collaboration software, for the plugin's In the form of eclipse, visual studio, etc.)   
 
 
 "  REST  " 
 This quick and dirty Bash script works with bamboo, I tested it for the Spring Framework Rest API:  
  echo" Revision Date Test X "Icho" -------------------------------------------- - --------------- "url = https: //build.springsource.org/rest/api/latest/result curl -qs $ {url for buildNumber in 1000..980 } / SPR-trunkhopshot - $ {Build Number} \ | Sed 's /^.* state = "\ (. * \)" Key. * BuildcompletedTime \ (. * \) .. creation full time. * VcsRevisionKey \. (. * \) .. vcsRevisionKey * $ / \ 3 is parsing the XML using the worst part  sed  (side note: this is a kind Linux shell) \ t \ t \ 2 \ t \ 1 / echo done   
 XPath / XSLT does not provide built-in command-line tools,  c'mon , this is XXI century!), But it works:  
  Revision Date Test X Status ----------------------------------- --------------- ----------- 4086 2011-03-13T01: 09: 13.319-08: 00 Successful 4083 2011-03-12T01: 05: 49.145-08: 00 Successful 4081 2011-03-11T01: 04: 46.9 4 9 08: 00 Successful 4074 2011-03-10T01: 09: 11.003-08: 00 Successful 4069 2011-03-09T01: 10: 17.766-08: 00 Successful 4069 2011-03-08T01: 09: 34.492-08: 00 Successful 4069 2011-03-07 Tate 06: 43: 51.054-08: 00 Successful 4068 2011-03-07 Tate: 3: 50: 41. 9 08-08: 00 Fail 4068 2011-03-07 T-00: 53: 55.523-08: 00 Unfair 4060 2011-03 -06 T 01: 06: 50.758-08: 00 Fail 4060 2011-03-05T01: 08: 35.477-08: 00 Successful 4057 2011-03-04T01: 08: 52.870-08 : 00 Cycle Undoubtedly 4056 2011-03-03T01: 10: 00.473-08: 00 Successful 4056 2011-03-02T01: 09: 15.679-08: 00 Successful 4055 2011-03-01T01: 13: 19.06 9: 00 Successful 4051 2011-02 -28T01: 08: 32.165-08: 00 Successful 4050 2011-02-27 T & A: 59: 33.392-08: 00 Successful 4050 2011-02-26 T01: 15: 01.113-08: 00 Successful 4036 2011-02-25T01: 09: 35.420-08: 00 Successful 4032 2011-02-24 T01: 13: 29.997-08: 00 Successful 4030 2011-02-23T00: 56: 51.656-08: 00 Failure   
 Jenkins also has support, so it's your own You should not take more than 30 minutes to re-write the code.