0
Testing of TL feature via API

1
100
1
1
2
101
2
1
2
102
3
1
2
1
100
4
fill in data with values that do not generate error/conflicts
1
2
101
5
fill in data with values that do not generate error/conflicts
1
2
2
100
6
create a custom field, then click export, then click cancel
1
2
101
7
create a custom field, then click export, then click cancel
1
2
3
4
1
Check that configuration controlled by&nbsp;input_dimensions.conf

100
8
controlled by:

[navBar] TESTPROJECT_TRUNCATE_SIZE=50
1
2
101
9
[mainPage] TESTPLAN_TRUNCATE_SIZE=45
1
2
5
1
2
100
10
1
2
101
11
1
2
6
7
/** Testauite:<br /> Fill in:<br /> <table border="0"> <tbody><tr><td>Title</td><td>Scope</td></tr> <tr><td>Author name</td></tr> </tbody></table> <br /> **/

100
12
1
2
8
9
10
11
Access to Documentation included on test link distribution

100
13
Choose a document and display it
1
2
12
0
1
14
Create Platform that have same NAME that existent ONE on this test project =&gt; Conflict
1
2
2
15
Create Platform without Conflicts
1
2
1
100
16
Check effects of adding ONE platform to a test plan that HAS NO Platforms, after test plan has been populated with test cases, and some test cases has been executed.
Have a test plan with test cases and some test cases executed
1
2
101
17
Verify that saving platform assignment with RIGHT PANEL empty does not create problems
1
2
13
1
2
0
100
18
1
2
101
19
Create Req Choose version 1 and create new version
1
2
101
20
<p>Create a Req.</p><p>Create several versions 1,2,3, making content of every version different</p><p>Choose version 2 =&gt; create a new version&nbsp;</p><p>&nbsp;</p>
1
2
1
103
100
21
Import a CVS that has a contain that assure no conflict will be generated by import. Fill User interface in following way: Leave combo "Set conflict solution" with it's default value [ ] Do not import items with empty Scope
1
2
101
22
Re-Import a CVS file, in this way you will create a conflict. Fill User interface in following way: combo "Set conflict solution" => UPDATE [ ] Do not import items with empty Scope
1
2
102
23
Re-Import a CVS file, in this way you will create a conflict. Fill User interface in following way: combo "Set conflict solution" => SKIP [ ] Do not import items with empty Scope
1
2
3
100
24
Creating a relation from REQ A to REQ A is not allowed => message must be displayed to user
1
2
101
25
easy means create a relation that will not have problems, for a REQ that has no relation defined
1
2
102
26
easy means create a relation that will not have problems, for a REQ that has relations defined
1
2
14
/** Testauite:<br /> Fill in:<br /> <table border="0"> <tbody><tr><td>Title</td><td>Scope</td></tr> <tr><td>Author name</td></tr> </tbody></table> <br /> **/

15
16
17
18
19
20
21
1
100
27
1
2
101
28
1
2
102
29
1
2
22
23
100
30
1
2
101
31
<p>Create a test plan using the create from feature</p><p>all checkbox of elements to copy UNCKECHED&nbsp;</p>
1
2
102
32
<p>Create a test plan using the create from feature</p><p>all checkboxs CHECKED</p>
1
2
103
33
<p>Create a test plan using the create from feature</p><p><span style="font-family: 'Trebuchet MS', Verdana, Arial, sans-serif; font-size: small; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px" class="Apple-style-span"><table border="0" style="text-align: left"><tbody><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Test Cases</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Builds</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">YES</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Priorities</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Milestones</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy User Roles</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Platforms Links</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">YES</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Assigned To</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr></tbody></table></span></p>
1
2
104
34
<p>Create a test plan using the create from feature</p><p><span style="font-family: 'Trebuchet MS', Verdana, Arial, sans-serif; font-size: small; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px" class="Apple-style-span"><table border="0" style="text-align: left"><tbody><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Test Cases</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">YES</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Builds</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">YES</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Priorities</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Milestones</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy User Roles</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Platforms Links</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">YES</td></tr><tr><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">Copy Assigned To</td><td align="left" style="vertical-align: top; padding: 3px; margin: 0px">&nbsp;</td></tr></tbody></table></span></p>
1
2
24
<p>All test project management feature.</p><p>Remember to test with and without platforms&nbsp;</p>

0
35
After a FRESH Install, create the first test project
CUCHI CUH
1
2
1
36
After a FRESH Install, create the first test project
CUCHI CUH
1
2
2
37
Create a Test project with all required information, without creating any conflict (use a test project name not present on system, use a PREFIX not present on system)
CUCHI CUH
1
2
3
38
1
2
5
39
<p>Choose an ACTIVE test project</p><p>Set INACTIVE</p><p>Choose again same test project</p><p>Set ACTIVE&nbsp;</p>
1
2
7
40
Delete a test projects that has NOTHING INSIDE
1
2
8
41
Delete a test projects that has NO PLATFORMS DEFINED
1
2
9
42
Delete a test projects that has PLATFORMS DEFINED, BUT NOT ASSIGNED TO ANY TEST PLANS
1
2
10
43
<p>Delete a test projects that has:</p><p>Custom fields, Keywords</p><p>platform defined an assigned to test plans</p><p>Test cases with custom fields</p><p>&nbsp;</p>
1
2
11
44
<p>Create a Test Project that has many test suites, but all are empty.</p><p>Test Project has:</p><p>&nbsp;</p><p>. no platforms</p><p>. no keywords</p><p>. no custom fields </p><p>. no requirements</p><p>. no inventory items</p><p>. no test plans</p><p>. no builds</p><p>. no milestones </p>
1
2
25
1
26
1
Create, Edit, Delete, Copy, Move, Import, Export operations

100
45
1
2
101
46
1
2
101
47
1
2
102
48
<p>Simple Means:&nbsp;</p><p>No keywords assigned</p><p>No Custom Fields &nbsp;</p>
1
2
102
49
1
2
103
50
1
2
103
51
1
2
104
52
easy means NO NAME CONFLICT
1
2
105
53
<p>Test suite has to have&nbsp;keywords assigned.</p><p>No Custom Fields &nbsp;</p>
1
2
106
54
<p>Test suite has to have&nbsp;Custom Fields&nbsp;</p><p>NO keywords assigned.</p><p>&nbsp;</p>
1
2
107
55
<p>Test suite has to have&nbsp;keywords and&nbsp;Custom Fields &nbsp;assigned</p><p>&nbsp;</p>
1
2
108
56
simple means Test Suite contains ONLY test cases Test Suite has NO keyword assigned Test Suite has NO Custom Fields Test Cases has NO keyword assigned Test Cases has NO Custom Fields
1
2
109
57
simple means Test Suite contains ONLY test cases Test Suite has keywords assigned Test Suite has NO Custom Fields Test Cases has NO keyword assigned Test Cases has NO Custom Fields
1
2
2
0
58
Create a test case DO NOT ADD STEPS Delete
1
2
1
59
1
2
2
60
1
2
3
61
1
2
3
62
<p>Copy Keywords: NO</p><p>Copy Requirements: NO&nbsp;</p>
1
2
4
63
easy means without generation errors or conflicts
1
2
5
64
1
2
6
65
1
2
7
66
1
2
8
67
1
2
3
1
1
0
68
1
2
1
69
1
2
2
2
4
1
100
74
1
2
101
75
1
2
5
27
100
70
1. Create some testcases with multiple versions and add to a testplan 2. Click Link &quot;Update Linked Test Case Versions&quot; 3. Expand Tree to Testcase level 4. Select single Testcase
1
2
101
71
1
2
28
29
Work on test case versions assigned to test plan, and assign users responsible of execution (testers)

0
72
<p>Test execute assignment to user</p>
<p>Test plan with a least one test case.</p>

<p>At least two users.</p>

<p>At least two platforms connected to the test plan</p>
1
2
- 1
  <p>Assign a test case on platform A to a user A and the same test case but platform B to user B</p>
  <p>Test case platform A is assigned to user A and platform B is assigned to user B</p>
- 2
  <p>Reassign a test case to another user</p>
  <p>Test case is assigned to the other user</p>
- 3
  <p>Unassign the test case</p>
  <p>The test case is unassigned</p>
1
73
<p>Test execute assignment to user</p>
<p>Test plan with a least one test case.</p>

<p>At least two users.</p>

<p>No platforms in use for the test plan.</p>
1
2
- 1
  <p>Assign a test case to a user</p>
  <p>Test case is assigned to the user</p>
- 2
  <p>Reassign a test case to another user</p>
  <p>Test case is assigned to the other user</p>
- 3
  <p>Unassign the test case</p>
  <p>The test case is unassigned</p>
1
100
1
1
1
2
101
2
1
<p>Create a issue tracker with a name that will generate collision.</p> <p>TL&nbsp;has to provide clear and human readeble, feedback message</p> <p>issue tracker attributes Type and Configuration, has to be preserved after feedback messages</p> <p>Check non event on TL&nbsp;event viewer</p>
1
2
102
3
1
1
2
103
4
1
<p>Similar to 'Create issue tracker - NAME&nbsp;Collision'</p>
1
2
104
5
1
<p>Check that 'delete icon' is present ONLY&nbsp;if issue tracker has not be linked to test project.</p> <p>Value of Active attribute on issue tracker integration on test project IS&nbsp;IGNORED</p>
1
2
105
6
1
<p>Check that 'delete icon' is present ONLY&nbsp;for issue trackers NON&nbsp;linked to test project</p>
1
2