|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Maybe you have the biggest automated test suite integrating Jenkins and TestLink?![]()
So far I've used with 20, 40 test cases.
> Maybe the probleme comes from best practices ?
> Is it common to have build plan with several hundreds of automatic tests ? Is it the way we are supposed to proceed ?
Someone should write about that. I'm not aware of best practices for this, but I think if the API returned all the custom fields at once, together with the test cases, then we would not have this issue.
Regardless of whether it's a good practice or not, it would work (though the response size would increse a bit).
And I think a regression test plan is very likely to include a lot of tests, unless you give a hint on what parts of the system changed.