|Anonymous | Login | Signup for a new account||2019-06-20 06:12 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007409||TestLink||New Feature||public||2016-01-12 11:46||2016-03-29 21:04|
|Product Version||1.9.14 (2015 Q3)|
|Fixed in Version|
|Summary||0007409: Ability of creating abstract testcases|
|Description||It would be nice to have a feature to create abstract test cases. |
Furthermore in my opinion this will be feasible by giving the test cases the ability to define variables (like attachments) in each test case and then by having a ghost string adding them into summaries, conditions or steps.(A ghost string [variable][/variable] maybe?
I think such a feature will speed up copying and changing similar test cases and make it even more comfortable.
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
|your requirement need to be detailed better in order to understand if can be implemented and how|
edited on: 2016-01-14 12:21
I'll give it a try.
In the newest version Testlink has the new function to add attached pictures via "ghost string" and the image id. Furthermore, all test cases are pretty "static", meaning that if you copy a testcase you usually (or very often) need to configure the steps of the new copied test case. However, most of the time these are only a few parameters such as different names for GUI-components, entities, databases etc. That means that the main structure of the steps is pretty much the same.
Now I thought - to make testcases a bit more "dynamic" - it would be a great feature if you add a new type of attachment called "variables" for each testcase. In each testcase you then can add variables, they will be stored in the background with a unique id and with this id you can add them to steps, preconditions and summaries of your testcase. By copying the testcase you then only have to configure the variables rather than editing every single summary, precondition and step over and over again. Example:
Let's assume we have testcase PRO-1 and testcase PRO-2. PRO-2 is a copy of testcase PRO-1. The Summary of both testcases is the following.
"This testcases checks if Page [variable]1[/variable] works correctly."
Now you see that we have added a variable. In the testcase you then can edit this variable so the ghost string would be replaced with the value of the variable. The user only needs to change the variable instead of changing the summary and all other parts of the testcase. Let's assume the following:
Value variable 1: "a123"
Summary: "This testcase checks if Page a123 works correctly."
Value variable 1: "B456"
Summary: "This testcase checks if Page B456 works correctly."
I think this would make Testlink even more flexible as it already is!
Important: For these variables the same text editors (like in steps, preconditions and summary) would be needed to add font-style to the variables and make them more compatible with the connected text.
If you need more information, just let me know.
Think solution can be using Custom fields.
Addin tag to get cf value.
Create feature to import just cf values on a test case.
Will work on this on next months (no eta).
|2016-01-12 11:46||T-Eberle||New Issue|
|2016-01-12 19:29||fman||Note Added: 0024409|
|2016-01-13 06:08||T-Eberle||Note Added: 0024411|
|2016-01-13 13:19||T-Eberle||Note Edited: 0024411||View Revisions|
|2016-01-14 12:21||T-Eberle||Note Edited: 0024411||View Revisions|
|2016-01-15 12:31||fman||Note Added: 0024415|
|2016-03-28 09:21||fman||Issue cloned: 0007485|
|2016-03-28 09:21||fman||Relationship added||related to 0007485|
|2016-03-29 21:04||fman||Assigned To||=> fman|
|2016-03-29 21:04||fman||Status||new => feedback|
|Copyright © 2000 - 2019 MantisBT Team|