424662 - Testopia 2 - cannot create dependencies for a test case

Status: RESOLVED FIXED

(Testopia :: Test Cases, defect)

Description

[Liliana Sambotin]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; InfoPath.2)
Build Identifier: 

Cannot create dependencies for a test case

Reproducible: Always

Steps to Reproduce:
1.open testopia at http://landfill.bugzilla.org/testopia2
2.go to test plan (ex: 601)
3.go to test cases tab and go to a test case (ex:784)
4.go to dependencies tab
5.there is no way to add dependencies for the current test case
Actual Results:  
cannot add dependencies for a test case

Expected Results:  
you should be able to add dependencies for a test case

Comment 1

[Greg Hendricks]

This works from the dependencies tab, but the page is not refreshed automatically. The changes don't show up till you refresh.

Comment 2

[Lisa Dickinson]

I have similar problem - big need to provide for order in which test cases are executed.  Depends on and Blocks can be populated but do not actually work as advertised in Runs:  you can Pass a test case that depends on a previous one without passing the predecessor.  Same for Blocks.  You can use ID as proxy for order -- but only if you load the cases in order and never have to inserte a new case step at a subsequent date.  Searching to see if someone else has this listed as a bug...

Comment 3

[Greg Hendricks]

(In reply to comment #2)
> I have similar problem - big need to provide for order in which test cases are
> executed.  Depends on and Blocks can be populated but do not actually work as
> advertised in Runs:  you can Pass a test case that depends on a previous one
> without passing the predecessor.  Same for Blocks. 

I am wondering where this "advertised", but the way it works is test cases that depends on another test case will be automatically marked BLOCKED if that dependency case fails. There is nothing from preventing a dependent case from being PASSED before the dependency.

> You can use ID as proxy for
> order -- but only if you load the cases in order and never have to inserte a
> new case step at a subsequent date.  Searching to see if someone else has this
> listed as a bug...

You may want to look at the Index field in the run. This allows you to set a custom order that test cases should be run in. Again, it does not enforce it, but at least you can see which cases ought to be done first. the request has been made to be able to sort test case based on dependency, but I have been struggling with a way to convert that to a usable SQL query.