Mantis Bugtracker          
testlink.org

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008182TestLinkTest Executepublic2018-01-16 11:222018-01-16 23:04
Reporterkostgr_2 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusfeedbackResolutionopen 
PlatformOSOS Version
Product Version 
Fixed in Version 
Summary0008182: Execution history in the test execution view is a little bit confusing for "Show only last execution" mode
DescriptionWe've found it a little bit confisung, that the table with execution properties and with links to execution reports is not available in the "show only the last execution" mode if there is newer build and the option(s)

$tlCfg->exec_cfg->show_last_exec_any_build = TRUE;
$tlCfg->exec_cfg->show_history_all_builds = TRUE;

are set.

Much more confusing was the effect of "show only the last execution" if the option $tlCfg->exec_cfg->show_history_all_platforms is on and the build was executed on another platform.
Steps To ReproduceFirst issue (show current build, previous build was tested):
1. Options $tlCfg->exec_cfg->show_last_exec_any_build should be set.
2. Execute test case A for some build
3. Create new build, close the previous one
4. Go to the execution of the test case A for the new build.
5. Execute test case B for new build

Now compare the execution view for test cases A and B with the setting "show only last execution".
=> the Table with link to test execution report is only available for executions for current build, not for executions of previous build.

Second issue:
1. Option $tlCfg->exec_cfg->show_history_all_platforms is on
2. Execute test case A on platform C
3. Go to execution of test case A for platform B
4. Activate "show only the last execution" mode

=> no execution is shown.

Additional InformationThe issues in the bug tracking system contain only the links to the execution view and the developers have to find execution reports from there.

If we open the new version for testing (new build), then the previous build is closed.
It was a bit confusing that the last execution was should as text, but not shown in the table with link to execution report.
Developer had to use "history on" button to become the list of all executions.

If the tested build is the current one, then the developer sees a link to execution report directly from the execution view.


We've fixed the issue with following two commits:
https://github.com/kostgr/testlink-code/commit/63346d86c9ace61f920a8eebf30b20727f4c34c4 [^]
and
https://github.com/kostgr/testlink-code/commit/3e46d5b7a1a6266c90b86e0f83ffe78d71539c97 [^]

The commits are unfortunately combined with the coloring of non-current builds in the execution history table.
TagsNo tags attached.
Database (MySQL,Postgres,etc)everyone
Browser
PHP Version
TestCaseID
QA Team - Task Workflow Status
Attached Files

- Relationships

-  Notes
(0027153)
fman (administrator)
2018-01-16 23:04

Dear user, IMHO you use in your issues too generic sentences like 'a bit confusing', that do not allow to understand in a simple way what is happening.
Same is valid for ISSUE SUBJECT, decreasing value of subject.

old build, new build are IMHO bad choices, please create issue description that seems more a test case, I.E:

Create BUILD B1, bla bla
Create BUILD B2 , etc

do not ask to compare things but add an screen shot were you make difference clear

The more time you spend creating a detailed issue report, higher the chance the issue will be analized to be included on WORKING QUEUE

Please provide ALWAYS testlink version.

Pull Request must follow a simple rule to be considered ONE PULL REQUEST HAS TO REFER TO JUST ONE TICKET or will be rejected

- Issue History
Date Modified Username Field Change
2018-01-16 11:22 kostgr_2 New Issue
2018-01-16 23:04 fman Note Added: 0027153
2018-01-16 23:04 fman Status new => feedback



Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker