Testlink Study Six: summary of TestLink1.9.13 work use

1, the default when the test case has the same name, you will be prompted. (Previous versions need to modify configuration)

2. Test Case Serial Number: ( disadvantage )

1) After deleting a test case, the subsequent number will be added 1 again, the number cannot be modified. (unless the database is modified)

2) The test case can be moved up and down manually, but the serial number is unchanged

3, test case set is not limited to three levels, can have multilevel, and the same level can exist simultaneously test case sets and test cases.

4. Milestones are not very useful for the time being.

5. Add a test case to a test plan: it is only the relationship between the test case and the test plan, no version management. (Must understand)

usage Scenario : You need to assign all of its test cases to test plan 1 at work.

workaround : You need to add the test cases that need to be included in the test plan, that is, the test plan includes all of the test cases, which may be performed by different versions.

6. Assign execution test case: test plan, version, use case, performer's relationship. (Must understand)

Usage Scenarios : Test plan V6.3, version RC1, smoke test.

workaround : What use cases are required to set up the appropriate user after the performer of the use case, and the use case for the user is not set up on behalf of this version, which is not included in the statistics, and is not counted in the use cases that have not yet been executed.

7. User role:

1) The role set by default for the user does not represent a real role in the actual project. You can modify the user role in the project plan, and the app will be based on the role in the test plan.

2) The user role of self-registration is the default of guest.

3) Admin user also did not see the password permission of other users. If you forget your password, you can send an email to the other user.

8. Assign a role to the test plan:

usage Scenarios : Different projects need to participate in the test is not the same people, how to set?

Workaround : Assign the list of test plan roles to include all users, in use, if a user does not participate in the program, you can set the user's test plan role to "no permissions"; If you want a tester to be a Test manager, You can modify its test plan role to leader.

Legacy Issues :

1, Testlink and Jira integration, I did not succeed.

2, Testlink and FCKeditor have not succeeded.

3, follow-up research under testlink and mantis integration.

Testlink Study Six: summary of TestLink1.9.13 work use