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)

]]>

Create a Test Plan
Create some Test Cases and add it to the Test Plan

Create 2 Builds B1 and B2.

In Build B1 - assign test cases to User A and User B

User A executes the test cases as below in build B1

Pass - 5
Failed - 3
Not Run - 8

User B executes the test cases as below in build B1

Pass - 8
Failed - 2
Not Run - 4

Now I need to assign the test cases to the build B2 for following requirements:
1: Add all not run test cases: This part works using the filters.
2: Add all the Pass test cases which were assigned to User A in the build B1 the test cases returned are incorrect.

The Filters I set for this are as follow:
Build to Assign : B2

Assigned to : User A
Status: Passed in specific build B1.

I hope this is clear. Let me know if any doubts.

You can try testing with other status values . They also return incrrect values or 0 test cases sometimes , If i remove the Assigned to USer A filter then the test cases returned are correct but are for all the assigned users.

]]>

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

]]>

Test using the test case ID filter

]]>

Create Test Project -> Project A ->Give Prefix of test cases as "QA"
Create Test Plan-> Test Plan 1 -> NO PLATFORMS
Create Build -> 501122
Create user -> user1 , role->senior tester
Create Test suite A and add test cases TC1 to TC5 sequentially.
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 "Test Case ID" filter -> Enter Value 5

]]> The Test case five should be displayed. the test case ID of the fifth test case should be QA-5

]]> Once the test case is filtered. Click on "Reset Filter"

]]> The filtered test cases should be cleared and whole left tree with all test cases should be displayed.

]]>

This test case is to test if exact test case title is given in filter is working fine or not

]]>

Create Test Project -> Project A
Create Test Plan-> Test Plan 1->NO PLATFORMS
Create Build -> 501122
Create user -> user1 , role->senior tester
Create Test suite A

Create Test case 1 -> with test case title as " Test case to test the filters"

Create Test case 2-> with test case title as " Test case 2"

Create test case 3 -> with test case title as "Test case to test the testcases"

Add test cases and assign test cases to user1
Login with user1 credential
Go to -> Test execution
Mark Test case 1 as Passed

Go to filters-> Select-> Test case title filter-> give "test case"

]]>

As all the three test cases has test case in them all the three test cases should be filtered.

]]> Reset the filters. And now give filter as "2"

]]> Only the second test case should be displayed.

]]> Reset the filter and now give the filter as "filter"

]]> Only the first test case should be displayed.

]]>

Filter by Test Suite

]]>

Create Test Project -> Project A
Create Test Plan-> Test Plan 1->NO PLATFORMS
Create Build -> 501122
Create user -> user1 , role->senior tester
Create Test suite A-> Test cases TC 1 to TC5

Create Test Suite B-> Test Cases TC6 to TC8

Add and Assign all test cases to user1

Go to -> Test execution

Mark TC 1 and TC 8 as Passed

Go to filters-> Select-> Test Suite Filter -> Test Suite A

]]> All test cases irrespective of status pass/fail/block in Test Suite A should be displayed

]]>

If a Test Plan does not exist in the list of Test Plans, adding the Test Plan should not cause a conflict error message to appear to the right of the Test Plan name field.

]]>

A Test Plan with the same name does not exist in the list of Test Plans.

]]> Click the Project tab.

]]> The Project landing page.

]]> Click the Test Plan Management link.

]]> A list of Test Plans.

]]> Click the Create button.

]]> The add new Test Plan form is visible.

]]> Enter a Test Plan name that does not exist in the list of Test Plans.

]]> An error message noting a conflict does not appear to the right of the name field.

]]> Enter a description in the Description field.

]]> Click the checkbox to the right of the Active field.

]]> A checkmark is visible in the checkbox.

]]> Click the checkbox to the right of the Public field.

]]> A checkmack is visible in the checkbox.

]]> Click the Create button.

]]> A Test Plan with your specified name is visible in the list of Test Plans.

]]>

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

]]>

In the issue 3987, we added the feature to upload attachments to test plans.

As administrator or leader, a user can now attach any file (text file, image, etc) to a test plan.

No warnings should appear in the event log viewer.

]]>

Administrator, leader or some other role with permission to manage test plans.

]]> Create a new test plan

]]> A new test plan is created

]]> Select just created test plan and edit it (is only way to access the attachment feature)

Upload an attachment

]]> The screen is reloaded when the popup is closed, and the attachment is displayed, with a delete button in the right side.

]]> Verify that no errors appeared in the apache log or in event viewer.

]]> No warning logs (specially regarding uninitialized variables)

]]>

In the issue 3987, we added the feature to upload attachments to test plans.

A user with rights to create test plans can now attach any file (text file, image, etc) to a test plan.

No warnings should appear in the event log viewer. And if a test plan is deleted, the attachments of this test plan must be deleted as well.

]]>

Administrator, leader or some other role with permission to manage test plans.

]]> Create a new test plan

]]> A new test plan is created

]]> Select just created test plan and edit it (is only way to access the attachment feature)

Upload an attachment

]]> The screen is reloaded when the popup is closed, and the attachment is displayed, with a delete button in the right side.

]]> Verify that no errors appeared in the apache log or in event viewer.

]]> No warning logs (specially regarding uninitialized variables)

]]> After taking notes of the test plan ID, we delete the test plan, and check that in the upload area (in the server), the attachments were deleted as well (you will have to use the test plan ID).

]]> Attachments are gone.

]]>

Create a test plan copied from another test plan with no attachments. Both must have no attachments.

]]>

User with rights to create test plans.

An existing test plan with no attachments.

]]> Create a new test plan, and check the option to copy from an existing test plan that contains no attachments. Leave the default copying settings.

]]> A new test plan is created, with no attachments.

]]>

Copy a test plan with attachments. Both test plans must have the same attachments.

]]>

User with rights to create test plans.

An existing test plan with attachments.

]]> Create a new test plan, and check the option to copy from an existing test plan that contains attachments. Leave the default copying settings.

]]> A new test plan is created, with the same attachments from the existing test plan.

]]>

Copy a test plan from another test plan with attachments, but do not check the option to copy attachments. This must leave the new test plan with no attachments, while the existing test plan remains the same, with attachments.

]]>

User with rights to create test plans.

An existing test plan with attachments.

]]> Create a new test plan, and check the option to copy from an existing test plan that contains attachments. Uncheck the option to copy attachments.

]]> A new test plan is created. While the existing test plan contains attachments, the new test plan must have no attachments.

]]>

Verify that a default informative message exist when there are no test plans.

]]>

A project with no test plans.

]]> Create a new project

]]> A project with no test plan.

]]> Click the Test Plan Management link.

]]> No test plan listed with the message " There are no Test Plans defined! Create one to allow test execution functionality"

]]>

If a Test Plan exist in the list of Test Plans, adding the Test Plan should cause a conflict error message to appear to the right of the Test Plan name field.

]]>

A Test Plan with the same name does exist in the list of Test Plans.

]]> Click the Project tab.

]]> The Project landing page.

]]> Click the Test Plan Management link.

]]> A list of Test Plans.

]]> Click the Create button.

]]> The add new Test Plan form is visible.

]]> Enter a Test Plan name that does not exist in the list of Test Plans.

]]> An error message noting a conflict does not appear to the right of the name field.

]]> Enter a description in the Description field.

]]> Click the checkbox to the right of the Active field.

]]> A checkmark is visible in the checkbox.

]]> Click the checkbox to the right of the Public field.

]]> A checkmack is visible in the checkbox.

]]> Click the Create button.

]]> The following error message appear at the top of the page.

"There is already a Test Plan with this name. Please choose another name!"

The system does not save conflicting Test Plan.

]]>

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