MantisBT - TestLink
View Issue Details
0000507TestLinkNew Featurepublic2006-11-26 03:142008-06-26 15:47
lowfeature requestN/A
0000507: [multiple steps] - Test Specification: Separete steps and results
I'd like to see and manage test case steps and result for each step in their own fields. Adding new steps between old steps should be essential, too.

Like this:

 Step 1 | Result 1
 Step 2 | Result 2
 Step 3 | Result 3
 Step 3 | Result 4
One way to implement this is to manage steps and results with some delimitter in database fields and use Javascript to manage this in UI.
No tags attached.
related to 0000422closed fman [multiple steps] - possibility to split execution steps 
related to 0001191closed mhavlat Possibility to upload test-proofs 
related to 0001310closed fman [multiple steps] - Multiple test steps and expected results 
jpg ST19.jpg (149,439) 2008-02-18 23:20
Issue History
2006-11-26 03:14mhalttuNew Issue
2007-02-19 23:23mhavlatProjectTestlink 1.6.x => TestLink
2007-09-16 05:08mhavlatNote Added: 0002150
2007-09-17 13:33fmanNote Added: 0002156
2007-09-17 14:18mhalttuNote Added: 0002157
2007-09-17 14:35fmanNote Added: 0002158
2007-09-17 16:10mhavlatNote Added: 0002160
2007-09-17 16:23fmanNote Added: 0002161
2007-09-24 05:01mhavlatNote Added: 0002218
2007-09-24 05:01mhavlatPrioritynormal => low
2007-09-24 05:01mhavlatStatusnew => acknowledged
2007-09-24 05:01mhavlatSummarySeparete steps and results => Test Specification: Separete steps and results
2007-09-24 05:11mhavlatRelationship addedrelated to 0000422
2007-11-20 06:40mhavlatRelationship addedrelated to 0001191
2008-01-23 15:29fmanRelationship addedrelated to 0001310
2008-01-23 17:19fmanStatusacknowledged => assigned
2008-01-23 17:19fmanAssigned To => fman
2008-01-30 16:30fmanSummaryTest Specification: Separete steps and results => [multiple steps] - Test Specification: Separete steps and results
2008-02-18 23:20DaniloFile Added: ST19.jpg
2008-06-26 15:47mhavlatStatusassigned => closed
2008-06-26 15:47mhavlatNote Added: 0003730
2008-06-26 15:47mhavlatResolutionopen => duplicate

2007-09-16 05:08   
That's like TestDirector behaviour. I'm not sure if this issue is not duplicated.
2007-09-17 13:33   
I think this can be an interesting feature, but needs DB schema changes and we ned to figure the effort to change a lot of code regarding getting test case info.
2007-09-17 14:18   
I think that bd schema changes could be avoided, if some xml could be used in formatting steps and results. Of course than needs some coding for user interface, but that could be done as an option, maybe. So server side is "as usual", but some installations could use different "test case editor" to save test case steps and resulsts as xml into db.
2007-09-17 14:35   
I don't like using XML to create a DB inside the DB, to manage what IMHO must be a DB change.
My vote to do this development using XML is No, I prefer to maintain the data model as clear as possibile => change schema.
2007-09-17 16:10   
we discuss it two years ago. I also suggest to use xml to structure it. But other core developers disagree, so nobody do anything.
I still think that it's the best way.
2007-09-17 16:23   
I will try write a proposal, trying to compare pro and cons of both solution,
with code impacts.
after this, we can discuss what and when to do.

IMHO is not a critical issue.
2007-09-24 05:01   
I moved this to state acknowledge. It seems that there is agreement that the feature is useful. However implementation is unclear.
2008-06-26 15:47   
Guys, I'm closing this record as duplicated to 1310. Please, set monitoring these issue 1310 if you interesting in a progress. Thanks