View source for QA Tools/Testlink

==Introduction==
For managing test cases, QA team uses Testlink (external site [http://www.testlink.org Testlink Home Page]).

==Customization==
For best suiting the tool to Openbravo ERP's processes, a new functionality was added to Testlink.

===User histories===
====User history 1====
A community user wants to participate on functional testing, so she opens testlink. Since is her first access, she does not have an account, so she choose the "Sign up for a new account" link. After that, she can login into the testlink and browse the testcases. She can now view what others did, the results of previous executions and execute testcases. She can freely choose between non executed testcases, already executed testcases (either by her or others). Execution can be successful (result: PASS) or unsuccessful (result: FAIL). In the last case, she can report an issue on the issue tracker ( [http://issues.openbravo.com link to issue tracker] ).

====User history 2====
An Openbravo QA engineer needs a new private site for feeding testcases for his own projects, and wants to keep control about who browse and execute his testcases. So he creates a new testlink project, marking it as Private, and providing access only to himself, a coworker and his manager. Since there are two modules for executing, he assign himself to one and left the other to his coworker.

===Implementation===
A new column was added to TestProjects table:
* Column: option_private
* Type: TinyInt
* Length: 1
* Default: 0

And a new function was added on the userCreate.php file:
* hidePrivateProjects.
** This function will override default TestLink by inserting a "<no rights>" role to each Private project. Table: User_TestProjects_Role.

On the Project Page, a new Combo for choosing is Private or not was added.

==Improvements==
*The <no rights> id used when inserting is hardcoded.
*When adding a new private project, no inserts are made on user_testprojects_role, so current users will have access if no manually limited.
*Changing a project to private (or to public) has no effect on current user clearance.


[[Category:QA Tools ERP]]