0
Testing of TL feature via API

1
100
1
1
1
2
101
2
1
1
2
102
3
1
1
2
1
100
4
1
fill in data with values that do not generate error/conflicts
1
2
101
5
1
fill in data with values that do not generate error/conflicts
1
2
1
100
76
1
1
2
101
77
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
78
1
1
2
103
79
1
<p>Similar to 'Create issue tracker - NAME&nbsp;Collision'</p>
1
2
104
80
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
81
1
<p>Check that 'delete icon' is present ONLY&nbsp;for issue trackers NON&nbsp;linked to test project</p>
1
2
2
100
6
1
create a custom field, then click export, then click cancel
1
2
101
7
1
create a custom field, then click export, then click cancel
1
2
3
0
86
1
<p>Try to displays event filtered by one or several users.</p>
<p>Event viewer right.</p> <p>Events available.</p>
1
2
1
87
1
<p>Try to display events filtered by date.</p>
<p>Event viewer right.</p> <p>Events available.</p>
1
2
2
88
1
<p>Try to display events filtered by level.</p>
<p>Event viewer right.</p> <p>Events available.</p>
1
2
3
90
1
<p>Try to display events filtered by all conbination between User, Level and date.</p>
<p>Event viewer right.</p> <p>Events available.</p>
1
2
4
89
1
<p>Try to delete events filtered by all conbination between User, Level and date or not filtered.</p>
<p>Event viewer right.</p> <p>Event management right.</p> <p>Events available.</p>
1
2
4
1
Check that configuration controlled by&nbsp;input_dimensions.conf

100
8
1
controlled by:

[navBar] TESTPROJECT_TRUNCATE_SIZE=50
1
2
101
9
1
[mainPage] TESTPLAN_TRUNCATE_SIZE=45
1
2
5
1
2
100
10
1
1
2
101
11
1
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
1
2
101
<p>This test suite is focused on verifiying behaviour of Testlink login under out of limit values</p>
100
82
1
<p>Try to set Login / Password with real Unicode values.</p>
<p>DB in unicode collation.</p>
1
2
Test involving login page
Test based on limit value.
101
83
1
<p>Try to set Login /&nbsp;Password with very long strings (&gt; 2048 chars).</p>
1
2
Test involving login page
Test based on limit value.
102
84
1
<p>Try to set Login /&nbsp;Password with empty or invisible (as #255 ascii char ) values.</p>
1
2
Test involving login page
Test based on limit value.
103
85
1
<p>Try to set Login /&nbsp;Password with HTML&nbsp;or PHP&nbsp;or JS codes inline.</p>
1
2
Test involving login page
Test based on limit value.
8
9
10
11
Access to Documentation included on test link distribution

100
13
1
Choose a document and display it
1
2
12
0
1
14
1
Create Platform that have same NAME that existent ONE on this test project =&gt; Conflict
1
2
2
15
1
Create Platform without Conflicts
1
2
1
100
16
1
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
1
Verify that saving platform assignment with RIGHT PANEL empty does not create problems
1
2
13
1
2
0
100
18
1
1
2
101
19
1
Create Req Choose version 1 and create new version
1
2
101
20
1
<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
1
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
1
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
1
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
1
Creating a relation from REQ A to REQ A is not allowed => message must be displayed to user
1
2
101
25
1
easy means create a relation that will not have problems, for a REQ that has no relation defined
1
2
102
26
1
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
100
91
1
1
2
- 1
  <p>Login to test link</p> <p>Create a test project</p> <p>Create Test Spec importing using sample present on</p> <p>[TL install dir]\docs\qa_data\simple_with_platforms\testproject-2ts-4tc.xml</p>
  <p>test spec with two test suites each with a child test suite, with two test cases inside each childe test suite</p>
  1
- 2
  <p>Create at least 4 users (you can use SQL&nbsp;script present on</p> <p>[TL_install_dir]\docs\qa_data\formula_one.sql or formula_one_mysql.sql)</p>
  <p>4 user + admin user</p>
  1
- 3
  <p>Create test plan PLAN-5111</p> <p>Create build 1.0</p>
  1
- 4
  <p>Use link on main screen ' Add / Remove Test Cases'</p> <p>select child test suite</p> <p>on right screen check first test case,</p> <p>select a use and a build</p> <p>(see attached image screen before ...)</p>
  1
- 5
  <p>Click button 'Add /&nbsp;Remove selected'</p>
  <p>after submit you will see NO&nbsp;INFO&nbsp;ABOUT&nbsp;tester assignment,</p> <p>but row with selected test case on step 4, will change color to yellow (see screen AFTER&nbsp;....)</p>
  1
- 6
  <p>Go to feature ' Assign Test Case Execution'</p> <p>look for test case used on step 4</p>
  <p>you will see that user is assigned</p> <p>(see image screen of Assign Execution feature)</p>
  1
20
21
1
104
100
27
1
1
2
101
28
1
1
2
102
29
1
1
2
105
<p>Not run is an special execution status, because NO&nbsp;RECORD&nbsp;IS&nbsp;WRITTEN&nbsp;into DB. For this reason is much more easier to written wrong queries.</p> <p>Special care has to be put on this kind of test cases</p>
103
94
1
<p>Not run is an special execution status, because NO&nbsp;RECORD&nbsp;IS&nbsp;WRITTEN&nbsp;into DB. For this reason is much more easier to written wrong queries.</p> <p>Special care has to be put on this kind of test cases</p> <p>&nbsp;</p>
<p>Test Plan has to have:&nbsp; Just One Build (1B), No Platforms (0P)</p>
1
2
- 1
  <p>Create Test Project -&gt; ISSUE&nbsp;5131<br /> Create Test Plan-&gt; Test Plan 1 - NO&nbsp;PLATFORMS<br /> Create Build -&gt; 501122<br /> Create user -&gt; user1 , role-&gt;senior tester<br /> Create Test suite A and test cases TC1 to TC5<br /> Add test cases and assign test cases to user1<br /> Login with user1 credential<br /> Go to -&gt; Test execution<br /> Mark Test case TC1 as Passed<br /> Go to filters-&gt; Select in Results-&gt;&quot;Not Run&quot; filter<br /> &nbsp; </p>
  <p>It should display 4 test cases as not run</p>
  1
104
95
1
<p>Not run is an special execution status, because NO&nbsp;RECORD&nbsp;IS&nbsp;WRITTEN&nbsp;into DB. For this reason is much more easier to written wrong queries.</p> <p>Special care has to be put on this kind of test cases</p> <p>&nbsp;</p>
<p>Test Plan has to have:&nbsp; Just One Build (1B),&nbsp; Just One Platform (1P)</p>
1
2
- 1
  <p>Create Test Project -&gt; ISSUE 5131</p> <br /> <p>Create Test Plan-&gt; Test Plan 2 - ON&quot; PLATFORM</p> <br /> <p>Create Build -&gt; 501122</p> <br /> <p>Create Platform -&gt; VxWorks</p> <br /> <p>Assigne Plaform to Test Plan</p> <br /> <p>Create user -&gt; user1 , role-&gt;senior tester</p> <br /> <p>Create Test suite A and test cases TC1 to TC5</p> <br /> <p>Add test cases and assign test cases to user1</p> <br /> <p>Login with user1 credential</p> <br /> <p>Go to -&gt; Test execution</p> <br /> <p>Mark Test case TC1 as Passed</p> <br /> <p>Go to filters-&gt; Select in Results-&gt;&quot;Not Run&quot; filter</p>
  <p>It should display 4 test cases as not run</p>
  1
22
23
100
30
1
1
2
101
31
1
<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
1
<p>Create a test plan using the create from feature</p><p>all checkboxs CHECKED</p>
1
2
103
33
1
<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
1
<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
1
After a FRESH Install, create the first test project
CUCHI CUH
1
2
1
36
1
After a FRESH Install, create the first test project
CUCHI CUH
1
2
2
37
1
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
1
2
5
39
1
<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
1
Delete a test projects that has NOTHING INSIDE
1
2
8
41
1
Delete a test projects that has NO PLATFORMS DEFINED
1
2
9
42
1
Delete a test projects that has PLATFORMS DEFINED, BUT NOT ASSIGNED TO ANY TEST PLANS
1
2
10
43
1
<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
1
<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
1
2
101
46
1
1
2
101
47
1
1
2
102
48
1
<p>Simple Means:&nbsp;</p><p>No keywords assigned</p><p>No Custom Fields &nbsp;</p>
1
2
102
49
1
1
2
103
50
1
1
2
103
51
1
1
2
104
52
1
easy means NO NAME CONFLICT
1
2
105
53
1
<p>Test suite has to have&nbsp;keywords assigned.</p><p>No Custom Fields &nbsp;</p>
1
2
106
54
1
<p>Test suite has to have&nbsp;Custom Fields&nbsp;</p><p>NO keywords assigned.</p><p>&nbsp;</p>
1
2
107
55
1
<p>Test suite has to have&nbsp;keywords and&nbsp;Custom Fields &nbsp;assigned</p><p>&nbsp;</p>
1
2
108
56
1
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
1
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
1
Create a test case DO NOT ADD STEPS Delete
1
2
1
59
1
1
2
2
60
1
1
2
3
61
1
1
2
3
62
1
<p>Copy Keywords: NO</p><p>Copy Requirements: NO&nbsp;</p>
1
2
4
63
1
easy means without generation errors or conflicts
1
2
5
64
1
1
2
6
65
1
1
2
7
66
1
1
2
8
67
1
1
2
9
92
1
<p>check how windows i opened</p>
1
2
10
93
1
<p>See 5121: [1.9.4 PREVIEW] Link to test case execution edit page is invalid</p> <p><a href="http://mantis.testlink.org/view.php?id=5121">Access issue on mantis (use RIGHT&nbsp;CLICK)</a></p>
1
2
3
1
1
0
68
1
1
2
1
69
1
1
2
2
2
4
1
100
70
1
1
2
101
71
1
1
2
5
27
100
72
1
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
73
1
1
2
28
29
Work on test case versions assigned to test plan, and assign users responsible of execution (testers)

0
74
1
<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>
  1
- 2
  <p>Reassign a test case to another user</p>
  <p>Test case is assigned to the other user</p>
  1
- 3
  <p>Unassign the test case</p>
  <p>The test case is unassigned</p>
  1
1
75
1
<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>
  1
- 2
  <p>Reassign a test case to another user</p>
  <p>Test case is assigned to the other user</p>
  1
- 3
  <p>Unassign the test case</p>
  <p>The test case is unassigned</p>
  1