I'm trying to setup TestLink suites that identify software by components/functions instead of going by requirements.
Here is a basic Example of the TestLink suite tree:
[CoolSoftware]
>[Menu01]
>>[Funciton01]
>>[Function02]
>[Menu 02]
>>[Function01]
>>[Function03]
In this example, Function01 appears in two GUI locations of the software. Is there a way to link these two Function01 together so that any action to one of them will be replicated in the other (like adding test cases)?
Test suites as software components/functions
Moderators: Amaradana, TurboPT, TL Developers