Mantis Bugtracker          
testlink.org

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006874TestLinkTest Execution - Bulk Modepublic2015-01-05 06:592015-01-06 07:50
Reporterswang3 
Assigned Tofman 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.9.11 (2014 Q2 - bug fixing) 
Fixed in Version1.9.13 (2015 #1) 
Summary0006874: Execution Order in Bulk Mode doesn't match with Order shown in Left test suite tree
DescriptionIn Test Execution - Bulk Mode, the execution order is sorted by test case ID. This doesn't match with the node order in the left test suite tree (The node order may be adjusted and it's not sorted by test case ID). This brings confusion to tester and it's hard for them to find a test case in left suite tree when there are many test cases inside a test suite.
Steps To ReproduceEnter "Test Execution" and select the last Test Suite to enter Bulk Mode.
TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL
Browser
PHP Version
TestCaseID
QA Team - Task Workflow StatusREADY FOR TESTING
Attached Files

- Relationships
child of 0006609closedfman Availables hot-fixes for 1.9.12 & How To get full fixed package from gitorious 

-  Notes
(0022448)
fman (administrator)
2015-01-05 18:48

please provide steps to reproduce as explained on forum.testlink.org.
we need to be sure we both are working on same scenario.
(0022449)
fman (administrator)
2015-01-05 21:04

https://gitorious.org/testlink-ga/testlink-code/commits/075bdaf6759aeabea6ddbd65e359ca046dc2198d [^]
(0022453)
swang3 (reporter)
2015-01-06 01:54

Steps To Reproduce:
1. Enter "Test Specification" and adjust the test case order a test suite.
2. Plan test cases under this test suite into a test plan.
3. Enter "Test Execution" and select this Test Suite to enter Bulk Mode.
4. Test case order shown at right doesn't match with the order shown at left (tree view).
(0022455)
fman (administrator)
2015-01-06 07:50

Dear sir
I've solved the issue but I need to said again than details to reproduce are not what expected.
Steps to reproduce has to be a GOOD TEST CASE and this is not the case
Take in consideration for future reports to avoid waste of time.
The less the effort the reporter puts on his/her report, the less will be the effort dev team will put to consider issue.

- Issue History
Date Modified Username Field Change
2015-01-05 06:59 swang3 New Issue
2015-01-05 18:48 fman Note Added: 0022448
2015-01-05 21:04 fman Note Added: 0022449
2015-01-05 21:04 fman QA Team - Task Workflow Status => READY FOR TESTING
2015-01-05 21:04 fman Fixed in Version => 1.9.13 (2015 #1)
2015-01-05 21:04 fman Relationship added child of 0006609
2015-01-05 21:05 fman Status new => resolved
2015-01-05 21:05 fman Resolution open => fixed
2015-01-05 21:05 fman Assigned To => fman
2015-01-06 01:54 swang3 Note Added: 0022453
2015-01-06 07:50 fman Note Added: 0022455
2015-01-06 07:50 fman Status resolved => closed



Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker