best parctice for structuring projects...

[garifo]

Hi, I was wondering if users of TestLink could provide info on how they currently structure their project.

This is the way I was thinking of doing it:

Project Name
---->For Component - e.g. Functional (Functial, Validation, Unit, Security, Usability & Accessibility Testing...etc)
--------->For Category - part of application under test e.g. Login Page
------------------->Test Cases to Test the Funcionality of the Login Page ( this test cases would be based on the component under which it will be created (Functial, Validation, Unit, Security, Usability & Accessibility Testing...etc))

Aside from this I would still be assigning kewords witht the same name I used for the Componet...so for this example it would have Funcational Keyword attached to it.

Do you guys think this is a good approach? or is it redundant since the keyword can define the type of tests? The reason why I was thinking of doing it this way is that it will make it easier to identify the type of testing right away.

Thanks in advance for you input.

Garifo

[havlatm]

Test Specification structure depends on amount of test within. I think that your draft is usable. For one small project I used component level as type of tests (SRS 1.0, SRS 2.0, Component test, etc.). For large product should be component level used better (as you described).

We receive the freedom from 1.7 because there will be possible more levels and it\'s meen better structure.

I don\'t double the structure in keywords. IMHO It don\'t bring a value. I use it to specify special sets as is: regression testing, or test related to one large problem or solution, or customization for customer.