Forum

Test case and sessi...
 
Notifications
Retirer tout

Test case and sessions management

4 Posts
2 Utilisateurs
0 Reactions
1,940 Vu
(@cmarti)
Posts: 65
Active Member
Début du sujet
 
[#8882]

Hi everybody,

This item has probably been asked and answered a ton of time, but I can't find the answer.

I would like to do the following points in order to check the evolution of the verification of the object under test prior to its launch to prototyping.
[list=1]

  • Definition of all the tests needed to verify its behavior against its requirements (this is clear and easy)
  • Having its estimated work summarized into a "parent object"
  • List all the test cases into a test plan - is it the test session here?
  • Have a log of all test sessions launch over the test plan - I have here a big confusion in between the concept of test session and test plan for ProjeQtOr.
  • Have a way (e.g. with the automated integration files) to import the test results from the non-regression tool manager (e.g. Jenkins).
  • Have a summary report (could use the API if needed) that indicates by week the evolution of the test sessions (which by the way are at least done daily, somethimes more).
  • [list=1]

  • The report would ideally have the number of tests passes, failed, blocked, non executed. All stacked to obtain also the evolution of the number of test cases.
  • I hope that my description is clear, and obviously that we can somehow do it on the tool

    Thank you for your help.


     
    Posté : 1 Mai PM 12:055
    (@babynus)
    Posts: 14952
    Membre Admin
     

    [list=1]

  • Definition of all the tests needed to verify its behavior against its requirements (this is clear and easy)
  • Having its estimated work summarized into a "parent object"
  • It is the test session

  • List all the test cases into a test plan - is it the test session here?
  • Yes, It is the test session

  • Have a log of all test sessions launch over the test plan - I have here a big confusion in between the concept of test session and test plan for ProjeQtOr.
  • It is the "test case run" on the test session

  • Have a way (e.g. with the automated integration files) to import the test results from the non-regression tool manager (e.g. Jenkins).
  • You can import "TestCaseRun" through import or through API

  • Have a summary report (could use the API if needed) that indicates by week the evolution of the test sessions (which by the way are at least done daily, somethimes more).
  • You'll have to build the "history", as I don't think we have such report
    [list=1]

  • The report would ideally have the number of tests passes, failed, blocked, non executed. All stacked to obtain also the evolution of the number of test cases.
  • You'll find it on test session and several reports, but without "history"

     
    Posté : 2 Mai PM 16:055
    (@cmarti)
    Posts: 65
    Active Member
    Début du sujet
     

    Thank you Babynus for those explanation.
    But I'm still a bit in the dark here.
    Is there a part of the documentation giving an how-to or example of using the test cases, test sessions and test runs?

    I've also tried the test session summary, but I can't choose the test session, non is visible. I have the warning sign but without any information helping me to solve that missing item

    Finally I would like to add some information on the test run like the revision of the version control used for the run, or a seed (we are using randomized tests).
    Is it possible to do that? I can't find it on the customization plug-in.

    Thank you


     
    Posté : 30 Mai PM 13:055
    (@babynus)
    Posts: 14952
    Membre Admin
     

    Is there a part of the documentation giving an how-to or example of using the test cases, test sessions and test runs?

    User manual is quiter explicit ( https://manual.projeqtor.org/html_en/RequirementsTest.html?#test-sessions)
    We also provide some specific document during training sessions that gives accurate and pragmatic information...

    Finally I would like to add some information on the test run like the revision of the version control used for the run, or a seed (we are using randomized tests).
    Is it possible to do that? I can't find it on the customization plug-in.

    No


     
    Posté : 9 Juin PM 16:066
    Share:
    Retour en haut