Testing History

[Mark]

We'd like to be able to see how many tests passed and how many failed
during a sprint.

Our process is to create a test under a story and when the development
is done to test it. If it fails it is marked as such for development
to fix. When it's tested again, it will hopefull pass but we will have
lost the knowledge that it took two goes to get it right.

In the help text, there is this sentence:

"Actual results from each test execution can be logged for each test
so that a history of all test runs is built."

What does this mean? More generally, any advice on how to analyse
tests gratefully received.

Regards, Mark

[Maggie Bullington]

Generally the test trend reports will aggregate the results for a day, week or month (for instance, the Trend - Test Count by Status report on the Project or Sprint dashboard). If a test fails one day, and passes the next, that will show in the report, but if a test fails then passes in the same day, it will show as passed. If you just want to know all the tests that failed during a sprint, you can use the following API query to get a list of failures:

http://servername/v1instance/rest-1.v1/Hist/Test?sel=Name,Parent.Name,Status.Name,ChangeDate&where=Status.Name='Failed';Timebox.Name='Sprint1'

replace servername, v1instance with the right names, and replace Sprint1 at the end with the name of your sprint. You can also add a project filter by adding ;Scope.Name='MyProject' to the end of the query.

-Maggie

[Mark]

Thank you Maggie,

That helps.

Can you explain how one gets the results of external test runs into
V1?

Regards, Mark

On 24 Jun, 17:10, Maggie Bullington <maggie.bulling...@versionone.com>
wrote:

> Generally the test trend reports will aggregate the results for a day, week or month (for instance, the Trend - Test Count by Status report on the Project or Sprint dashboard). If a test fails one day, and passes the next, that will show in the report, but if a test fails then passes in the same day, it will show as passed. If you just want to know all the tests that failed during a sprint, you can use the following API query to get a list of failures:
>

> http://servername/v1instance/rest-1.v1/Hist/Test?sel=Name,Parent.Name...

>
> replace servername, v1instance with the right names, and replace Sprint1 at the end with the name of your sprint. You can also add a project filter by adding ;Scope.Name='MyProject' to the end of the query.
>
> -Maggie
>
>
>
> -----Original Message-----
> From: versiono...@googlegroups.com [mailto:versiono...@googlegroups.com] On Behalf Of Mark
> Sent: Tuesday, June 24, 2008 11:52 AM
> To: VersionOne-users
> Subject: Testing History
>
> We'd like to be able to see how many tests passed and how many failed
> during a sprint.
>
> Our process is to create a test under a story and when the development
> is done to test it. If it fails it is marked as such for development
> to fix. When it's tested again, it will hopefull pass but we will have
> lost the knowledge that it took two goes to get it right.
>
> In the help text, there is this sentence:
>
> "Actual results from each test execution can be logged for each test
> so that a history of all test runs is built."
>
> What does this mean? More generally, any advice on how to analyse
> tests gratefully received.
>

> Regards, Mark- Hide quoted text -
>
> - Show quoted text -

[Maggie Bullington]

External TestRuns can either be imported via the Excel import function, or input directly via the API. The Fitnesse integration and the QTP integration are examples of how this is accomplished. To get an idea of how this works, take a look at the docs for those integrations:
http://community.versionone.com/Downloads/Documentation/Fitnesse.aspx
http://community.versionone.com/Downloads/Documentation/QTP.aspx

There are also videos:
http://demos.versionone.com/video/FitNesse/FitNesse.html
http://demos.versionone.com/video/QTP/QTP.html