Forum

Requirement & Test ...
 
Notifications
Clear all

Requirement & Test Sessions

9 Posts
2 Users
0 Reactions
5,241 Views
ash
 ash
(@ashofphoenix)
Posts: 140
Active Member
Topic starter
 
[#5290]

Hi,
I've got a question regarding requirement and Test Session

As a matter of Fact, a Test session can be seen into planning but requirement can't. The only way to 'see' requirement is to attached it to a milestones or any test session, but it's not really my question.

A test session can be considered as a Cascade of Test Cases.. That's fine. You can prepare, every test cases, "join' them to a Test Session, and you have a summary of Cases... Just fine.

However, when you want to define a Requirement as a success of a Test Session, I don't manage to really do it.. You have to take back all test cases onto "list of test cases" of your requirement instead of taking only The Test session as "list of tes cases"...

Is there a way to define requirement either as a list of tests cases or as a Test Session in order not to have to grab again all the Test cases onto requirement definition and by this fact, grabing the summary of test cases of the Test Session "linked"...?

I try to define The requirement "origin" to the test Session but it seems useless.
I try to link my test session to the requirement, but it's only a way to obtain quicker link nut not result of test session ONTO the requirement directly...

BTW, Thanks for this Terrific software development !


 
Posted : 19 Jul 2018 17H30
(@babynus)
Posts: 14952
Member Admin
 

Is there a way to define requirement either as a list of tests cases or as a Test Session in order not to have to grab again all the Test cases onto requirement definition and by this fact, grabing the summary of test cases of the Test Session "linked"...?

No, such feature does not exist.


 
Posted : 19 Jul 2018 19H35
ash
 ash
(@ashofphoenix)
Posts: 140
Active Member
Topic starter
 

Could it be planned, because it's obvious that if you create a Full test session with plenty of test cases, you should take the test session as a requirement instead of taking all the test cases individually into the requirement definition ? (otherwise you will have to do it twice with possibles mistakes taking all test cases...)


 
Posted : 20 Jul 2018 11H34
(@babynus)
Posts: 14952
Member Admin
 

I think you describe it the other way round.
It's not a test session that will define tests cases for a requirement (mostly because ofter test session covers several requirements).
But I agree that the idea to define test session from requirements is good.
The idea would be to define test cases on the requirement (as of today) to define test cases covering the requirement.
Then, when you define a test session, you should be able to select the requirement (or requirements) you want to test in the test session, to automatically retreive test cases to play
Request recorded as Ticket #3504


 
Posted : 20 Jul 2018 11H42
ash
 ash
(@ashofphoenix)
Posts: 140
Active Member
Topic starter
 

That sounds nice and it will make it !

Just to talk, and for good understanding you said that a test session cover several requirements

For me I saw a requirement as a "project need" and I would have said that my "project requirement" can be severals test sessions success of my products (as those test sessions can be done in different places (e.g. CEM Test Session / Security Test Session / Hit Test Session .. etc.) and can be realy different

Maybe due to name use, " Test Case ", and as a technician , That will be the start of all.. Then I will do a "Test session" with "Test cases" which will be called for example "fonctionnal test session" , " CEM Test Session", etc. and the Requirement over all this for the project itself will be the success of all those test sessions.

Different points of views but the goal of all this is not to make twice the work so I also understand your approach 😉

BTW, Shoud be nice to be able to define a Milestone as a requirement ???? 🙂


 
Posted : 20 Jul 2018 13H08
(@babynus)
Posts: 14952
Member Admin
 

The requirements are not the project objective.
The project objective contains requirements.
And each "main" requirement can be divided into several functional and/or technical requirements.

To my point of view (exemple taken on software developement), a requirement can be very large : "Application must control access rights"
or very precise : "field X on screen Y is mandatory"


 
Posted : 20 Jul 2018 22H26
ash
 ash
(@ashofphoenix)
Posts: 140
Active Member
Topic starter
 

*bump* This #3504 ticket still looks like unimplemented ? Is there a possibilities in soon update or not ? 😛 ... Should be really nice to be able to take "requierement" as a source for test session ^^


 
Posted : 08 Apr 2020 11H59
(@babynus)
Posts: 14952
Member Admin
 

Hi,

This is not a priority for us today.
Only way to have it soon is to "sponsor" this evolution to have it on next release.
You can request for it on Contact form


 
Posted : 08 Apr 2020 12H49
ash
 ash
(@ashofphoenix)
Posts: 140
Active Member
Topic starter
 

ok, I guess it's not a priority as this tickets has at least 2Y :p
Gonna see If I can do something but I guess I will still have to wait...

Thx
Rgrds


 
Posted : 08 Apr 2020 14H32
Share:

Scroll to Top