Create a issue tracker with a name that will generate collision.

TL has to provide clear and human readeble, feedback message

issue tracker attributes Type and Configuration, has to be preserved after feedback messages

Check non event on TL event viewer

]]>

Similar to 'Create issue tracker - NAME Collision'

]]>

Check that 'delete icon' is present ONLY if issue tracker has not be linked to test project.

Value of Active attribute on issue tracker integration on test project IS IGNORED

]]>

Check that 'delete icon' is present ONLY for issue trackers NON linked to test project

]]>

Try to displays event filtered by one or several users.

]]>

Event viewer right.

Events available.

]]>

Try to display events filtered by date.

]]>

Event viewer right.

Events available.

]]>

Try to display events filtered by level.

]]>

Event viewer right.

Events available.

]]>

Try to display events filtered by all conbination between User, Level and date.

]]>

Event viewer right.

Events available.

]]>

Try to delete events filtered by all conbination between User, Level and date or not filtered.

]]>

Event viewer right.

Event management right.

Events available.

]]>

Fill in:

Title	Scope
Author name

**/ ]]>

This test suite is focused on verifiying behaviour of Testlink login under out of limit values

]]>

Try to set Login / Password with real Unicode values.

]]>

DB in unicode collation.

]]>

Try to set Login / Password with very long strings (> 2048 chars).

]]>

Try to set Login / Password with empty or invisible (as #255 ascii char ) values.

]]>

Try to set Login / Password with HTML or PHP or JS codes inline.

]]>

Create a Req.

Create several versions 1,2,3, making content of every version different

Choose version 2 => create a new version

]]>

UPDATE [ ] Do not import items with empty Scope]]>

SKIP [ ] Do not import items with empty Scope]]>

message must be displayed to user]]>

Fill in:

Title	Scope
Author name

**/ ]]>

Create a test project

Create Test Spec importing using sample present on

[TL install dir]\docs\qa_data\simple_with_platforms\testproject-2ts-4tc.xml

]]> test spec with two test suites each with a child test suite, with two test cases inside each childe test suite

]]> Create at least 4 users (you can use SQL script present on

[TL_install_dir]\docs\qa_data\formula_one.sql or formula_one_mysql.sql)

]]> 4 user + admin user

]]> Create test plan PLAN-5111

Create build 1.0

]]> Use link on main screen ' Add / Remove Test Cases'

select child test suite

on right screen check first test case,

select a use and a build

(see attached image screen before ...)

]]> Click button 'Add / Remove selected'

]]> after submit you will see NO INFO ABOUT tester assignment,

but row with selected test case on step 4, will change color to yellow (see screen AFTER ....)

]]> Go to feature ' Assign Test Case Execution'

look for test case used on step 4

]]> you will see that user is assigned

(see image screen of Assign Execution feature)

]]>

Not run is an special execution status, because NO RECORD IS WRITTEN into DB. For this reason is much more easier to written wrong queries.

Special care has to be put on this kind of test cases

]]>

Not run is an special execution status, because NO RECORD IS WRITTEN into DB. For this reason is much more easier to written wrong queries.

Special care has to be put on this kind of test cases

]]>

Test Plan has to have: Just One Build (1B), No Platforms (0P)

]]> Create Test Project -> ISSUE 5131
Create Test Plan-> Test Plan 1 - NO PLATFORMS
Create Build -> 501122
Create user -> user1 , role->senior tester
Create Test suite A and test cases TC1 to TC5
Add test cases and assign test cases to user1
Login with user1 credential
Go to -> Test execution
Mark Test case TC1 as Passed
Go to filters-> Select in Results->"Not Run" filter

]]> It should display 4 test cases as not run

]]>

Not run is an special execution status, because NO RECORD IS WRITTEN into DB. For this reason is much more easier to written wrong queries.

Special care has to be put on this kind of test cases

]]>

Test Plan has to have: Just One Build (1B), Just One Platform (1P)

]]> Create Test Project -> ISSUE 5131

Create Test Plan-> Test Plan 2 - ON" PLATFORM

Create Build -> 501122

Create Platform -> VxWorks

Assigne Plaform to Test Plan

Create user -> user1 , role->senior tester

Create Test suite A and test cases TC1 to TC5

Add test cases and assign test cases to user1

Go to -> Test execution

Mark Test case TC1 as Passed

Go to filters-> Select in Results->"Not Run" filter

]]> It should display 4 test cases as not run

]]>

Create a test plan using the create from feature

all checkbox of elements to copy UNCKECHED

]]>

Create a test plan using the create from feature

all checkboxs CHECKED

]]>

Create a test plan using the create from feature

Copy Test Cases
Copy Builds YES
Copy Priorities
Copy Milestones
Copy User Roles
Copy Platforms Links YES
Copy Assigned To

]]>

Create a test plan using the create from feature

Copy Test Cases YES
Copy Builds YES
Copy Priorities
Copy Milestones
Copy User Roles
Copy Platforms Links YES
Copy Assigned To

]]>

All test project management feature.

Remember to test with and without platforms

]]>

Choose an ACTIVE test project

Set INACTIVE

Choose again same test project

Set ACTIVE

]]>

Delete a test projects that has:

Custom fields, Keywords

platform defined an assigned to test plans

Test cases with custom fields

]]>

Create a Test Project that has many test suites, but all are empty.

Test Project has:

. no platforms

. no keywords

. no custom fields

. no requirements

. no inventory items

. no test plans

. no builds

. no milestones

]]>

Simple Means:

No keywords assigned

No Custom Fields

]]>

Test suite has to have keywords assigned.

No Custom Fields

]]>

Test suite has to have Custom Fields

NO keywords assigned.

]]>

Test suite has to have keywords and Custom Fields assigned

]]>

Copy Keywords: NO

Copy Requirements: NO

]]>

check how windows i opened

]]>

See 5121: [1.9.4 PREVIEW] Link to test case execution edit page is invalid

Access issue on mantis (use RIGHT CLICK)

]]>

Test execute assignment to user

]]>

Test plan with a least one test case.

At least two users.

At least two platforms connected to the test plan

]]> Assign a test case on platform A to a user A and the same test case but platform B to user B

]]> Test case platform A is assigned to user A and platform B is assigned to user B

]]> Reassign a test case to another user

]]> Test case is assigned to the other user

]]> Unassign the test case

]]> The test case is unassigned

]]>

Test execute assignment to user

]]>

Test plan with a least one test case.

At least two users.

No platforms in use for the test plan.

]]> Assign a test case to a user

]]> Test case is assigned to the user

]]> Reassign a test case to another user

]]> Test case is assigned to the other user

]]> Unassign the test case

]]> The test case is unassigned

]]>

Copy Test Cases
Copy Builds	YES
Copy Priorities
Copy Milestones
Copy User Roles
Copy Platforms Links	YES
Copy Assigned To