ID Category Title

1 New user No validation of Polish characters

2 Sorting results Incorrect sorting in the columns by ID

3 Incidents Attachments - no thumbnail on the screen of the incident

report

4 Incidents Attachments - the ability to attach a file in a format not

provided for the specifications.

5 Incidents Incidents tab - incorrect display of incidents assigned to

the project.

6 Adding The ability to create a super adminstrator without

superadminstrator entering e-mail address.
account

7 Member list Member list does not refresh after changing the data of
currently logged in user.

8 Log on Invalid username displayed on the login screen when

selected options "Remember last username"

9 Editing a user The ability to edit the name of any user who is not a root.

10 Incidents Invalid text of the tooltip for add an attachment button.

11 Incidents The root user type does not have possibilities to view all
events - the list is empty.
11 Incidents

12 Incidents Incorrect option available for the incident with the status
"question" is assigned to the user for permission "tester".

13 New user The field "Name" allows to enter 64 characters

14 Log on Three wrong logon does not block the user account

15 Project Add a new project - an incorrect description of the field.

16 Project Prefix - the text pasted from the clipboard is not

converted to uppercase.

17 Project The project - the version, a component, an envirment -

max. 255 characters
18 Project The project - the user "tester" cannot be changed to the
project manager

19 Incidents The incident - change of status - from "in repair" to the

"information you need" - possibility to assign to a person
other than the tester.

20 Incidents The incident - change of status - the manager cannot

change from New to Duplicate/ No requirements

21 Project Impossible to add the user to the project

22 Project The project - the possibility to duplicate version name,

the component and the envirment

23 Project The project - removing versions, components or the

envirment after sorting elements in these windows.

24 Adding The window of root creation appears each time after

superadminstrator starting up the application till to set the administrator
account account

25 Adding Setting up the root account during instalation

superadminstrator
account

26 Project Administrators privilages to people management in the

project

27 Project Edition of projects logged on root and administrator.

28 Options Remembering the size and position of the application

window.

29 Incidents Incident - blank space at the beginning of the name of

the incident
30 New user The ability to define the same username for users.

31 Assigning users to a Wrong validation when adding a user to project

project
31 Assigning users to a Wrong validation when adding a user to project
project

33 Connecting with The "Connecting to database" window - field "Port" has a

database default settings

34 Connecting with The "Connecting to database" window - field "Username"

database remembers the incorrect text.

35 Connecting with The "Connecting to database" window - field "Server

database Address" remember incorrect text.

36 Adding Okno "root" - pole "Haso" nie akceptuje samych spacji.

superadminstrator
account

37 Incidents The "new incident" window - field "Description" has

incorrect validation.

38 Incidents The "Incidents" - the option from the main menu

"Change the assgned person" does not work

39 Editing a user Name field allows to enter an apostrophe sign.

40 Sorting results Sorting works only within one page.

40 Sorting results Sorting works only within one page.

41 Assigning users to a Users tab - Users Projects - no possibility to remove the

project user from the project

42 Assigning users to a Users tab - Users Projects - changing the users role in
project the project

43 Projects User Manager - Projects tab - icons of project

management.

44 Projects User Manager - Project tab - Adding components and

environments

45 Editing a user "User/Edit" menu is grayed out for the currently logged in
user.
46 Projects The administrator can assign the same Manager for two
projects

47 Incidents Incidents - editing

48 Incidents Incidents - editing

49 First run After logging in, the user is not on the "Incidents" tab.

51 Connecting with Defining the database - no designation of the required

database fields.

52 Users Permissions - creating and deleting an administrator

account by another administrator.

53 Adding Screen - create a root account - the e-mail validation

superadminstrator
account
54 Incidents Create a new incident \ No scroll bar (vertical) with a
long description

55 Incidents The incident report \ "Close Report" icon - incorrect

tooltip description.

56 Creating user Validation of the "Name" field during creation a user

account

57 Users Closing the user removal window.

58 Incidents Possibility of viewing events in all projects.

60 Incidents The addition of an attachment to the incident

61 Project The incidents are not removed after removal the project

62 Project management root and administrator can not manage users in the
project.
63 Incidents Incidents - wrong person entered in the Change History
of incident

64 Incidents Incidents - incompability as to the capability to assigning

people in the incidents belongs to nonexistent project

65 Users Users - the system allows to create a new user with a

password exceeding 32 characters

66 Users Users - the system allows to create a new user with

NAME exceeding 32 characters

67 Projects Screen to create a new project - a typo in the name field

68 Projects Screen to create a new project - wrong field name

69 Projects Type on the popup confirming the deletion version of the

project.

70 Incidents Incidents - priority column is incorretly sorted

71 Adding Field superadmin user accepts digits during account
superadminstrator setup
account
72 Incidents The "Name" and "description" when creating an incident
allows to use any characters other than alphanumeric

73 Incidents The application does not allow to change the status of

the incident

74 Specyfication Text Box instead of the button.

75 Specyfication Incorrent button name in the specification

76 Specyfication No "OK" button in the specification of the project editing

screen.
77 Incidents A filtration does not act all over "Project" field on the
"Incidents" bookmark

78 Editing a user The ordinary user can change the own login name

79 Incidents It is not possible to open attachments, when the

application is being started from a few different locations

80 Incidents It is not possible to delete the attachment of the incident

81 Incidents Closed lack of requirements - lack of the option "new"

82 Incidents Closed off repaired - lack of the option "new"

83 Other At the attemp to start the application more than once the
error appears
84 Users In the view of the main window are visible icnompatible
with the specification buttons to set the number of
records displayed

85 Incidents Typo in "name" iin the History of incident

86 Incidents "Description" instead of "description of incident" in the

History of incident
87 Incidents unnecessary "(a)" in the History of the inciident

88 Incidents Typo in "attachments" in details of the incident

89 Incidents Lack of writing the incident of the person to which the

incident was assigned in history

90 Projects Wrong supplementing filed "project manager" on-screen

to create a new project

91 Incidents Excessed comma at the option "Lack of requirements,"

for the filter of incidents

93 Incidents Once the chosen version adds the incident, it cannot be

moved back

94 Users The application shows deleted user as the "project

manager"

95 Connecting with When first starting the user isn`t getting the feedback in
database case of entering incorrect data (e.g. password)
 95 Connecting with When first starting the user isn`t getting the feedback in
database case of entering incorrect data (e.g. password)

96 Connecting with Lack of marking required fields in the form of the

database connection to the database

97 Specyfication Typo in the specification page 12

98 Projects Typo in the tips for removing the user from the project

99 Specyfication Visibility of the bookmak users for the role of the ordinary
user

100 Specyfication Visibility of the bookmak "Projects" for the ordinary user

101 Incidents Wrong content of the message when I change the

person assigned to the incident

102 Users Invalid validation of the e-mail address field

103 Users According to specification (permission matrix) ordinary

user only has access to the login screen

104 Incidents Typo at the change of status of the incident

105 Specyfication According to the specification one of components should

be called "User" and is called "Users"
106 Specyfication According to the specification one of components should
be called "managing incidents" and is called "Incidents"

107 Specyfication Typo - in the specification "root" is written together but in

the application separately
108 Specyfication According to the specification history should have the
following appearance:
a. Jan Kowalski changed (s) status from Programming to
the Question.
b. Jan Kowalski changed the priority from Normal to
High.

109 Creating user Field "repeat the Password" does not show information
about the problem
109 Creating user Field "repeat the Password" does not show information
about the problem

110 Adding User name - allow characters out of the specification

superadminstrator
account

111 Incidents The person assigned to the project can edit it

113 Specyfication Project - Incident - the person assigned to the project

can edit the incident

114 Loging window Authorization - no icon on the taskbar

115 Incidents Adding a long comment

116 Connecting with Connecting to the database - new installation

database

117 Connecting with Connecting to the database - error messages

database
118 Users Delete the user

119 Incidents Window of incidents

120 Projects Adding the project - it is possible to create the new

project with the name longer than 36 (fo 5 characters)

121 Incidents No message about the fact that in the Description field
are inserted more than 1000 characters

122 Sorting results Sorting of lists with subpages

Reproduction steps
Logging on to the application as a root/adminstartor.
Entry to tab users. Click the "Add User". In the opened
window in the field "Username" type a name using Polish
characters ""
Log on to the system, sorted out the table in the User tab
by ID, sorted out the table in the Projects tab by ID,
sorted out the table in the Incidents tab by ID, sorted out
the table in the pop-ups by ID

Logging on to the application as the user assigned to the

project in which incidents are reported. Enter to the
incident tab. Double-click on the incident - open a
window with an incident report screen. Add an
attachment in png format
Logging on to the application as the user assigned to the
project in which the incidents are reported. Enter to the
incident tab. Double-click on the incident - open a
window with an incident report screen. Add an
attachment in docx format
Logging on to the application as a user with two projects
assigned. Entry to Projects tab. Select from drop-down
list one project.
Start the application for the first time after instalation.
Connect to the application database. On the "root"
screen fill all fileds with corret values except for the "E-
mail". Click the "OK" button.
Logging on to the application as root. Clicking in the
lower left corner of the drop-down list with the name of
currently logged in user. Edit user data and click on the
OK button.
a. Logging on account to the application as "root"
b. Select from main menu "Settings -> Options"
c. Select option "Remember last username"
d. Edit the currently logged in user data (especially
editing the "username")
e. Log out from the application.
a. Logging on account to the application as "root"
b. The addition of at least two users - one of type
"administrator" and the second type of "normal user".

c. Clicking on the list for the user to type "administrator".

d. Clicking on the "Edit seelected user"

e. In the edit form - change data in the fields "Name" and
"Last Name".
f. Clicking on the button "OK"
a. Logging on to the application as user with privilages to
add the incident to the project.
b. Clicking on the "incidents".
c. Adding a new incident.
d. Double-click on the incident added in steo "c".
e. Hovering the mouse cursor on the add an attachment
icon.
a. Logging on account to the application as "root"
b. The addition of at least two users (any type)
c. The creation of two new projects (assigned roles as
manager for users from "b" set)
d. Log out from the root account and log in to the first
user created in "b" step.
e. The addition of the new incident.
f. Log out from the application and log in as second
created user in "b" step.
g. The addition of the new incident.
h. Log out from the application and log in as root.
i. Clicking on the "incidents" tab.
a. Logging on to the tester account.
b. The addition of the new incident.
c. Log out from the application and log in as a manager
account.
d. Changing the status of the incident added in the step
"b" to "to repair".
e. Log out from the application and log in as repairs
account.
f. Change of status status notification from step "b" to
"Question" and assign the incident to the user of
"Tester" type
g. Log out from the application and log in as a tester
account.
h. Displays the details of the incident reported in step "b".

a. Opening Users tab

b. Press the icon "+" to add new user
c. Typing in the field "Name" string exceeds 32
characters, eg fkjdsjfkldsjfkjdskjldsKJAKLJKLSfjdsjf--
fkldsjfkljsdfkldsjfjdsklf
d. Fill all the other fields with any value which comply
with specification.
e. Press the button "OK".
When you log in, enter 3 times wrong password, then log
with in with correct data.
a. Clicking in the context menu "Project"
b. Select the "Add new project".
a. typing tex in the notepad (3-7 characters) eg abc.
b. copy the characters from the clipboard
(select>rmc>copy)
c. Ctrl+V to paste text from the clipboard to the field
"Prefix"
d. fill other fields and add the project
Initial conditions - the projest has been added
Steps:
a. Opening a bookmark design
b. Selection of the project
c. Expand menu "Project"
d. Select any from 3 options: versions, components or
the envirment
e. Click on the "+" key in the "Project version" window

f. Type 256 characters

a. Addition of project manager (user_1)

b. Adding to the project user with "user" privilages

(usr_2). Assigning the role of a tester to him
c. Edit the project and change the manager - select the
user (user_2), who is currently a tester
d. Press Ok
a. Open the incident in the status of the repair by the
repairer

b. incident > change status> needed information

a. th manager opens the incident
b. expand incident list > Change Status > closed >
duplicate / no requirements
- open the "Members Project" in the "Projects" tab
- press the button "Add user"
- type the first letter of any existing users and make sure
that a list was shown from 1 with only an element (with
user)
- press the button "OK" (IMPORTANT: do not choose the
user before from the list, click on it)
In the window "Project Version", "components of the
project" and " project environment" add the name of an
existing list
In the window "Project Version", "components of the
project" and "project environment" sort list
(independently by which column)
The first launch of the application or new installation.
Creatinon of the root account. Logging into the
aplication. Restart the aplication. A screen of creating the
root appears
Run the application

Log on as an administrator or a root. Go to the projects

tab

- run the application

- log in as the user
- change the size and position of the window
- close application
- run the application
- in th login window, press "Cancel"
- restart the application
- log in to the application
Create incident. In the name as the first sign put the
space
Create the user named 'user1'. Create 2nd user with the
same name 'user1'
- choose the user from the users list
- press the 4th icon on the left of Quick Menu
- after appearing of the new window, press the plus icon

- enter a name other than the previously-defined projects

also choose choose role
- press ok
Start the installation process of database (follow the
installation instructions)
After the completed installation start the application - a
window will appear "connecting to database"

- start the installation process of the database (follow the

installation instructions)
- after the completed installation start the application - a
window will appear "Connecting to the database"
- for all fields except the "Port" enter the values that
prevent a connection to the database, for example, the
string "AAAA"
- press the button "OK", and then "cancel" in order to
close the application
- start the application again
- start the installation process of the database (follow the
installation instructions)
- after the completed installation start the application - a
window will appear "Connecting to the database"
- for all fields except the "Port" enter the values that
prevent a connection to the database, for example, the
string "AAAA"
- press the button "OK", and then "cancel" in order to
close the application
- start the application again
- start the installation process of the database (follow the
installation instructions)
- after the completed installation start the application - a
window will appear "Connecting to the database"
- fill all fields up with correct values and press "ok"
-D:D- fill required fields up with valid values. In fields
"password" and "confirm password" enter 8 blank
spaces and press "ok"
- in the "incidents", press the plus button to add a new
incident
- after opening the window "New incident" fill all required
fields, type in "description" less than 10 characters, press
the "ok" button
1) On the Incidents screen slelect an incident
2) In the mian menu of application go to "incident" and
then select "change the assigned person"
1) on the users tab click the button to add a user (the
plus button)
2) fill only the field "name" with string "AA'AA"
3) press ok button
4) the application does not display the message of the
incorrect value for field "name

1) create more than 20 incidents, and set them to

different statuses
2) leaving the default paging of 20 items, sort by column
e.g "status"
3) verify the order of sorted elements on the front page

4) change the page and verify the order of the elements

on the other page
1) select a user on the Users tab
2) click on the icon "Projescts of the selected users"
3) in the above window, select the latest project from the
list
4) sort the projects after all sorts columns
1) Check the projects on the Project tab
2) Select the user in the Users tab
3) Click on the icon " Projects of the selected users"
4) In the above window, edit the users role in the project
for the project which he is the Manager
5) Change the user role to Tester / Repairer
6) Check the list of project on the bookmark Project
1) As the administrator change the role of the user in the
project from the Manager to the Tester / Repairer
2) Log in with manager account from above
3) Check the availabilyty of icons for project managment

1) Open a window of managing components

2) Move the cursor over the icon and wait utill a window
is shown with the description of the button
3) Open the menu and repeat the above actions on
menu items
4) Repeat the action on the managment environments
window
Select user on the list at currently logged on usser (root
or administrator)
In the Projects tab, assign one manager to two different
projects

Eddition of the incident - the description field

Click on the incident -> Edit the selected incident ->

Select version/component/environment -> click ok

Launch the apllication Mr Buggy -> Create a new

superuser account (fill fields up with data in accordance
with the specification -> click ok
First start the database

Launch the application -> login in as plain administrator -

> users -> add (or remove) a new user

Install a new instance of the apllication in accordane with

specification
Giving the required e-mail address to create
superadministrator account to the field of e-mail enter
special characters within e-mail address, eg
emai#$l@myemail.com
1. start the application
2. go to incidents tab
3. create a new incident (+) and open it using double-
click on it
4. fill in the required fields
5. Create the description, that does not fit in the current
view
1. start the application
2. create a new incident
3. move the coursour on the incon "Close Raport"
1. Open the Mr Buggy application
2. Log in as the administrato and in the "Users" window
(creating new user) go to field "name"
3. In the field "Name" type two characters "" "
(apostrophe and a space)
4. Press ok button
1. Open Mr Buggy application
2. Log on
3. Create a "plain user"
4. Select "plain user" and click "remove selected users"

5. In a newly opened window "removing users" click on

"x" in the right upper corner
Initial conditions
User with Administrator role has assigned projects and
the possibility of adding incidents
They are other users with assigned incidents

Reproduction steps
1. Open the Mr Buggy application
2. Log in as the administrator
3. Go to the incidents tab
4. Select a project assigned to this user
5. Set 2nd filter "not assigned to me"

- slect the incidents tab

- click on the grrn plus (add a new incident)
- double-click on the chosen incident
- add the system file as the attachment e.g. file from
Windows/System32/*.dll
- click on the name of the attachment which turns up
right after adding it in the incidents editor
- create a project
- to a previously created project add D187new incidents

- remove the project

User is loged in as root or administrator. At least one
project was added
Steps:
- Click on the "Projects" tab
- Click on the icon "Manage users"
1. Log in as Repaires to Mr Buggy
2. In the incidents module changes the status of the
incident assigned to me to Solved
3. Log in as the Project Manager
4. In the incidents module makes the edition of the
incident solved by the rapairer and changes his name

1. Add a valid project (Project >> Add)

2. Add the valid incident (incidents >>add)
3. Remove the project (Project >> Delete)
4. In the incidents tab see that insn`t able to rewrite the
person into the incident in a non-existent project
5. Display the choosen inciden (Incident >> View)
6. Change the status and assigned person
1. Log in to Mr Buggy as administrator
2. From the main menu select Users -> Add
3. Fill in all field with valid data
4. In the password field, enter the password that contains
more than 32 characters e.g.
mz123mz123mz123mz123mz123mz123mz1236789
5. Press OK

1. Log in to Mr Buggy as administrator

2. From main menu select Users -> Add
3. Fill in all field with valid data
4. In the Name field, enter a name containing more than
32 characters, e.g
abcdefgAHJJabcdefgAHJJabcdefgAHJJabc
5. Press OK

Context menu > Selection Project - > add

Context menu > Selection Project - > add

Projects tab -> click on the icon "version mangament" -

>on-screen with versions of project, select project ->click
on the icon "delete version"
Go to the Table of incidents and sort by criticality error
Field "user name" on the stage of the configuration ot the
superuser account

Field "name" while creating an incident

Change the status of the incident: Closed (no

requirements) -> New -> Action "New" enables to re-
open a closed incident

The page 11 of the specification describes the fields and

error massages that can be displayed on the screen
eddition of the project
The page 21 of the specification describes the available
buttons
The page 11 of the specification describes the screen of
the edition of the project
Initial conditions: create a minimum three projects and
add a few incidents to them
1. Go to Incidents tab
2. In the filter choose particular projects checking
whether the list of incidents is being narrowed to the
selected projects
- create an account of an "ordinary user" named "ccc"
from the administrator level
- log out from the root account
- log in as the user with "ccc" login name
- click on the user name at the bottom bar, click Edit,
enter any user name, click ok
- the login name has been changed
1. Start the application from the given location (e.g.
memory stick)
2. Log in as root
3. In th incidents tab add the new incident
4. Add attachments to the crated incident
5. Save the notification
6. Close the application
7. Copy the MrBuggy.exe file to another location (e.g
drive C)
8. Launch the application from the new location
9. Log in with data used before
10. Open the previously reported error
11. Open attachment from point 4.
Add an attachment to incident

Add an incident. Change the status to "lack of

requirements", next change to "lack of requirements
(closed)"
- add the incident
- change status to repair
change status to solved
- change status to re-test
- change status to closed (fixef)
After log in as one user try to run application second time
1. Install the Mr.Buggy application

2. Run the application and connect it to the database

3. Open the main application window

4. Pay attention to the upper right corrner of application

5. There are visible button of which should not be

The incidents tab. From the menu select Incident/
Display
The incidents tab. From the menu select Incident/
Display
The incidents tab. From the menu select Incident/
Display
The incidents tab. From the menu select Incident/
Display
1. Log in as tester
2. Report the incident and assign it to any user
3. Log out.
4. Log in as the project manager
5. From the list of incidents select the "change the
assigned person"
6. Assign the incident to another user
7. Check the history of changes
1. Log in as administrator
2. Create the user with data: name: user; password adn
repeat password: alamakota123; Name: User; Surname:
Testowy; E-mail address: user.testowy@mrbuggy.pl

3. Go to project tab
4. Opening the window of creating new project
5. Fill in the form fields: Prefix: tst; Name: Test;
6. In the field "Project Manager" start typing from "t", the
application itself should supplement the rest of the field
upon created user
7. Confirm the desire to add a project by pressing "enter"

1. Log in as any user with privilages to see the incidents

2. go to incidents tab
3. Verification of the status list to filter resulting list
1. Log on as user with privilages to add incidents to
project
2. Click to add an incident
3. Select from drop-down list version
a. the creation of the project -> project manager:
user_example
b. delete user "user_example"
c. view the tab Projects
1. Start the MrBuggy.exe for the first time
2. Select the chceckmark "New installation", fill in the
missing fields
3. Any of the fields "user name", "password", "server
address", "port", "name of the database" fill in with invalid
data - e.g. incorrect password or name of nonexistent
database
4. Press ok button
Go to the connect to the database window

The table on page 12 in the specification

1. Go to Projects. 2. Select the project and select

"manage users". 3. Select the user on the list and
hoverthe mouse pointer over the icon of removing the
account
Log in as the ordinary user

Log in as the ordinary user

1. Go to the incidents tab. 2. Add the incident and

change its status to repair and assign him e.g. for user
repairer1 3. Then, as the project manager change the
assigned person to user named repairer2. 4. Double-
click on the incident in order to see the history of
changes
1. Log in to the application as user with privilages to
create a new users
2. Choose the button add new user from users tab
3. Fill in all fields with valid data except e-mail address

4. Type in an e-mail address field the string containing

the Polish letters e.g. alla@wp.pl
1. As root creates an ordinary user account. 2. Log in as
ordinary user.

Perform the action on the incident: "closed off (of lack of

requirements)"
Log into the application on account of administrator

Log into the application on account of administrator

Log in as root and go to the users tab

1. Change the status of the incident

2. Change thr priority of the incident

3. Open the incident and go to the history

a. run the application after properly configured

b. after launch, open the "new user" window (green
button +)
c. in the window "new user" in field password enter
"1234567"
d. in replay password field enter "1234567"
e. click ok
The first launch of Mr.Buggy

Define the conncection to the database

The window "new administrator"

Fill the form with invalid data
Press ok
Create the project
Add users to the project
Create the incident
Log in as users with no assigned incidents
Edit the incident

Create the project

Add users to the project
Create the incident
Log in as users with no assigned incidents
Edit the incident

Log in to the application

Log ou using the lower menu
Add a long comment on the incident

Create a new database -> launch mr.buggy -> fill form

for database connection -> do not chceck "new
installation"

Click Settings ->New database-> enter the invalid login

data
There are at least two users on the list who can be
removed
There are at least two incidents on the list. Open them in
the separate widows

Log in as the administrator

Add the new project
Enter the name of the project on the max lenght

Create the incident

In the description field enter over 10000 characters.
Save the incident.
On the users/project/incidents list add record so that a
created new subpage of records
Select the name of the column to sort the results
Change the page of records
Current result
The field is not valid as correct

The rows are arranged in the incorrect order of the ID

value. The IDs value are grouped by the first digit, not by
the full value of ID. The problem occurs in the tabs
Users, Projects, Incidents, pop-ups liks Projects
Members.
After add an attachment the thumbnail does not appear.

Docx file is attached to an incident and can be open

correctly.

The person choosing one project from the drop-down list

sees results for all projects, choosing the second project
sees incorrect results for a choosen project.
Followed by the creation of user with superadministraotr
permissions without filled field "e-mail"

After the last step, the user list is not refreshed by the
changes entered in the last step.

After the "e" setp, the application displays the login

screen. The "username" will be completed with data
before step d.

After the "e" step, followed by saving the changes to user

data. According to application specifications (page 8),
should be possible only edit fields "Username" and "E-
mail"

After the "e" setp, the tooltip is displayed for the button.
However, it has incorrect and confusing text (mn_tooltip).

After "i" step empty list of incidents appears

After "i" step empty list of incidents appears

For the user , the only options available are add an

attachment and comment.

User has been added.

The Name field accepted 64 characters.

The user has been logged in.

The field is called "Add".

The project has been added with the prefix with

lowercase letters.

Unable to enter more than 255 characters

The pop-up has been closed and there are no error
messages.
The previous user (user_1) has left as the manager. The
changes have not been saved.

In the users list the notification can be attached not only

to the tester

action is not available, the field is inactive

After pressing the button "okay" an error message

appears: "the specified user doesn't exist". It is incorrect
announcement. New pressing the button "okay." does
not change the situation.

Ability to add duplicate names

Not possible to remove any of the element from these

windows

After creating a root account and does not vreate a new

account of admin, the application will be forcing to create
root account

The root account is defined during application start, not

during the installation("The first account - the root
account - is configured during the installation of the
product. The login name and the password being set at
the installation process")
The root and the administrator account can not manage
people in the project if they are not managers of these
project
Logged root and the administrator do not have the
access to the "add the project to the user" for their own
account
Localization and size of the window are not saved

The application allows for putting the space as the first

sign of the name of the incident.
There is a possibility of defining the same users

The tooltip for the field ptoject displays "The specified

user noes not exist"
The tooltip for the field ptoject displays "The specified
user noes not exist"

The port field has a default value

In th "User name" field displays previously entered text

In the field "Server Address" displays previously inserted

text

The application does not accept the same space in the

"Password" and "Confirm Password"

According to the documentation (section 11.1) the field

"Description" requires at least one character, while
currently you need to make al least 10 characters to
create an incident.

Selecting "Change the assigned person" from the main

menu does not display the window for changing the
assignment
In case of writing the apostrophe sign in the surname the
validation is passed correctly

Sorting covers only the range of data within a single

page. With more data sorting in this way is inconvenient.
Sorting covers only the range of data within a single
page. With more data sorting in this way is inconvenient.

For the last project from the list, edit and delete inactive
buttons. For other projects from the list the behavior is
correct. Sorting projects does not change the state of the
button for the above project, even though the project is
no longer at the end of the list
After changing the role from Project Manager to
Tester/Rapairer , the project for which the change was
made are disappear from the list of projects

In projects where the manager has been assigned to the

role of Tester / Restoration 4 icons of the project
mangament are inaccessible

After moving the cursor on buttons and positions on the

menu in windows managing components and managing
environments are shown as well as the description "add
the version" for all buttons and the option in the menu

Icons enabling the edition of the user are greyed as well

as buttons are greyed of the top menu User
With the help of the bookmark "Projects", in the tool
"Edition of the project" it is possible to assign the same
user as Manager of project in two projects
In the Description field pass to the down line using the
Enter - the incident is saved instead of a new line.

Although the incident has the assigned version,

component, environment, this information are not visible
amongst information describing this incident
After logging into MrBuggy, there is "Users" tab shown
for a user.

No mark required fields

Logging on to the ordinary administrator account I am

able to create (or removals) accounts for other
administrator
It Is allowed to use special characters such as '!' '=' '$'
'%'
When exceeding a amount of characters that can be
displayed in your edit Universal Box scroll bar does not
appear

"toolStripButton1" is visible

Space character at least is an allowed sign isn't being

counted at the validation of field "name" therefore "' "(the
apostrophe and the space) isn't fulfilling the validation of
2 signs.

the "x" in the upper right corner does not work for the
window "delete user"

the ability to view incidents in all projects

* additionally the user can edit incident from the project

to which he is not even assigned

Not served system exception attached to the

img/ddec3.png screen capture

incidents remain

(7.6 specification Matrix of entitlements):

A window appears 'Users of the project'
The person entered in the change history of the incident
as the author of the amendment made by the 'Edit
selected incident' will be the person who last changed
the status of the error, and is not logged in person. For
example a repairman changed the status of the incident
to 'Resolved', and the Project Manager's (another
person) changes the name of the incident by incident
highlighted Edition - in the history entry shows that the
incident changed the name of the repairer.

If there are a few incidents already reported in the given

project and next this project is removed, the manager of
the project can assign new persons to incidents, even
when this option is unavailable of the menu. It will be
sufficient to change the status of the incident and the
application alone will make such a possibility available. It
is a functional disagreement.

The system enables to create the new user with the

password which exceeds 32 signs (lack of the validation
for the maximum amount of signs).

The system enables to create the new user with the

name exceeding 32 characters

On the screen of creating a new project we have a field

name "Project Manager"
On the screen of creating a new project we have a field
named "Description"
a pop'up with a typo appears. We have "Are you sure
want to delete the version of the project ?"

In the table of incidents, column 'Priority' is sorting

according to the order/priority (starting than highest):
1. Blocker
2. Critical
3. Low*
4. Normal
5. Trivial
6. High*
The order of priorities of the 'Low' and 'High' is converted
during the sorting. The order of priorities in the combo
box when creating a new incident is correct.
The "login name" at the stage of the configuration of the
superuser account allowes to use digits

Field "Name" and the "Description" while creating the

incident allow tor use any characters other than
alphanumerical signs
Change of status of the incident: Closed off (lack of
requirements) - > New - > Action New however a user
enables the reopening of the closed incident not perhaps
to perform such an action.
Field project manager should be a button

The button Closed (repaired) is available

In the description there is "OK" missing

The list of incidents remains unchanged irrespective of

what project will be chosen

Possibility to change login name from the user level

A possibility to open the earlier added attachment

It is not possible to delete the once attached file as the

attachment to the incident
No option to change the status of the incident to the new
one

No option to change the status of the incident to the new

An error has occurred: The mr. buggy stopped working

In the right upper part of the screen additional buttons
and lists are visible

In the history of changes Content includes " ... has

changed the name of ... "
In the history of changes Content includes " ... has
changed the description . "
In the history of changes Content includes " ... has
changed ...", for the cases of a change of name /
environment
When there is/ priority / component
no attachment there/isversion / description
information "There
are no attachments"
In case of performing the change of assigning incidents
from user1 per user2 it will not stay recorded in the story
of changes of the incident

When filling out the "project manager" application itself

tells the user if we start supplementing the first letter of
his name. At the start of automatic writing prompt does
not change the size of the typed character by what you
can not automatically use the first hint by validating it
with the 'enter'.

There is a described option in the application as "Lack of

requirements,"

It will not be possible already to return to empty field with

the version, although it isn't required.

Non-existent uytkowink is being shown as the manager

of the project

The window is being reloaded saving entered data.

The window is being reloaded saving entered data.

In the database connection window the required fields

are not marked with "*". This is a field : password

On page 12 in the table with the field type there is "texts

field"
In the view of users of the project after moving the cursor
on red icon a wrong announcement appears

As log on as ordinary user on the upper menu I can see

the bookmark "Users"

As log on as ordinary user, without the given plan I can

see the bookmark on the upper menu projects.

Instead of information about the change of the assigned

person to the incident, information about the change of
status appears

In the email adress Polish letters can appear, provided

that the address is not started with them or finished.
Through the application e.g. alla@wp is an
acceptable address.Address, of which the application will
prevent will be e.g. al@wp. pl

The ordinary user can log onto the system.

Typographical error: "closed off (of lack of

requirements)"
In the application one of components is called "Users"

In the application one of components is called "Incidents"

In the column the "type" is written: "root"

The story is being saved in the application as follows:

a. Jan Kowalski changed status from [Programming] on

[Question]. - should not be of square brackets ([])
b. Jan Kowalski changed priority from "Normal" on
"High". - should not be quotes (""), should not be "(a)"
beside
Field "repeat the Password" isn't returning information
about the mistake.
Field "repeat the Password" isn't returning information
about the mistake.

There is an announcement in the application "Incorrect

login name. Allowed signs it is small and the upper case,
digits and signs:. _ - "

Error: The matrix of privilages lacks a specific right to

edit incident for the user to whom the incident is not
assigned

Error: The matrix of privilages lacks a specific right to

edit incident for the user to whom the incident is not
assigned

Error: a window of the authorization appears, but there is

no icon of the program on the taskbar. If other programs
are
It is open they aretohiding
not possible from
read the view
long of the window
comment. of bar
A scroll the
is missing
The application is breaking and an unsupported exerpt is
being shown. Additionally, after the click continue the
application is logging onto the user "User" and every
performed action is ending with the Unsupported
exception
Lack of any announcement of entering incorrect data

Mark two users and with click into the icon try to dismiss
them. One user will be removed
After the closing "X" of incident from the window with
incidents and another for adding it, it is not possible with
him to do nothing. All disabled icons and the lack of the
description.
Mistake: Name of the project - field is accepting 50 signs
and that's that is saved in the
qwertyuioapasdfghjkklzxcvbnmqaqwertyuioapasdfghjkk
application what is more than in documentation
The incident was written from 10000 signs, without the
error message.

Every subpage is being sorted individually.

The expected result
The field shoud pass correct validation

According to the specification: "In accordane with the

Convenction, it will be possible to sort the results by
each column." Elements of the table should be arranged
in the correct order by ID

According to the specification: "What is more, files with

JPEG an PNG extension will be displayed as thumbnails
on the screen containing reports of incidents." Afterr

According to the specification: "The following file types

are allowed as attachments: JPEG, PNG, TXT, DOC,
RTF, PDF, ZIP, RAR, 7Z, TXT, XML, XLS '- docx file
should not be attached to the incident.

Choosing a specific project in the table should show only

incidents from a given project.

According to the specyfication (page 7) for the root

account: "When creating the account should enter email
address on the configuration screen."

Position with the root data includes data before the last
step.

The application should remember the last loged in

username.

No ability to editing name.

Name for tooltip "Add an attachment".

According to the privileges table included in the

specification (page 9) root type user has the following
possibility: "Viewing incidents in all projects"
According to the privileges table included in the
specification (page 9) root type user has the following
possibility: "Viewing incidents in all projects"

According to the specification (page20) should be also

available options "To repair" and "To retest".

The Name field permits from 2-32 characters, small,

block letters and "-" signs. The field is required.

The user should be blocked and should not be able to

log in to his account.
According to the specification the field should be called
"Add New Project" (page 12 pts. 10 - the first sentence:
"When youfield
The Prefix clickshould
in the context menuas
be validated Project > Add
incorrect, or New
signs
shall be automatically converted to uppercase.

The specification provides for 256 characters (paragraph

10, version management)
It Should be possible to assign a tester as administrator

According to the specification, repairer can return

notification of "in repair" to "necessary information" only
to a tester.
No information about assign them to a manager
Should be able to change the above statuses . It is
available in the specification

It is possible to add a user

According to the specification a name must be unique "

names for versions , components and environments
must be unique. "
Possible removing elements from these windows

The application after creating the account of the root

should show the screen of the log-on

By permissions table on the page 8 of the specification

should be able to manage people in the projects, even if
they are not managers
According to the specification "Administrator has access
to the" Add project to the user ""

The last position of the window should be remembered

The specification forbids it: "the Name cannot begin from

the space."
According to the specification the name must be unique.

tooltip for field project with information: "the given project

doesn't exist"
tooltip for field project with information: "the given project
doesn't exist"

Documentation in the 5.1 point about it recalls nothing;

field should be empty after showing the window.

In field the "login name" is shown default value "root"

(documentation 5.1 point)

In field the "Address of the server" is being shown default

value "localhost" (documentation 5.1 point)

In fields "Password" and "Potwtrz password" it is

possible to write any signs down (according to. of
documentation)

The " Description" passes validation when you type one

character

Choosing an option "change the assigned person" from

main menu I invoke desired actions

In case of writing the apostrophe down in the surname

the application should show the error of the validation.

The sorting should sort the entire scope of data enabling

later to look only a scope through.
The sorting should sort the entire scope of data enabling
later to look only a scope through.

Possibility of removing the user from the project

After changing the role of the Project Manager for

theTester / Repairer projects should not disappear

Should be properly "Add Component" / "Add the

environment."

Ability to edit the user from the icons on the "Members"

page and the top menu "User"
According to the specification "project manager is a
person who manages a single project in Mr. Buggy
application".
After pressing the Enter the cursor oneself should move
line down.

After editing the incident by adding the version /

component / environment information should be
displayed in the preview window ofthe incident
According to the specification "MrBuggy-requirements",
point. 9, page 12, in such a situation tab
"incidents"should be displayed.
At first starting the database on the pop-up "connectiong
to the database" according to the specifications of the
fields "Name", "Server Name", "Port", "database name"
should be the star indicating the fields of duty

According to the specifications of the administrator

should have permission only to create (or delete)
accounts of ordinary users
Validation of e-mail does not allow to enter special
characters
At exceeding amount of signs which can to be shown in
edit box scroll vertical bar should appear

"Close the report" tooltip is visible

According to visible information at the validation of field

"name" allowed signs it is big both small letters and the
apostrophe and the space

The window "removing user" should be closed

Only superadministartor is able to look incidents through

in all projects

Possibility of the edition of the attachment (removal)

Incidents are removed

Nothing happens. The root / administrator is grayed out

options for managing users.
The entry in the history of changes in the incident always
indicates the right person who made the change.

An agreement should be as for the possibility of

manipulating the assigned incident for the non-existent
project.

Field the password should be validated in terms of the

maximum quantity of signs (to 32).

Field name should be valided in terms of the maximum

quantity of signs (to 32).

According to specification it should be Project

Manager'.
According to specification it should be project
description '
The word 'project' has not been properly transformed. It
should be: Are you sure you want to delete the version of
the project? '
The correct sort order (starting with the highest priority)
are:
1. Blocker
2. Critical
3. High
4. Normal
5.Trivaial
6. Low
The specification allows to use only letters and signs ". _ -
" (specification, ch. 5.2)

According to the 11.1 pt, p. of 14 specifications text box

"Name" and the "Description" allows to use from 10 to
255 alphanumeric characters.
The user should can perform such an action

Field project manager it should be a button and is a text

box.

The button close (repaired) is available

Description appears for "Ok" button

The list of incidents is restricted to the selected project.

Ordinary user only has the access to log on, as it is

apparent from the specification (page 8-9)

Application error when trying to open a file attachment

Possibility of the file deletion from the attachment

Possibility to change the status of the incident into a new

one

Possibility to change the status of the incident into a new

one

It should start with the second window with the

information that the application is already running
A regulation on implementing the functionality being
used to place displayed amounts does not exist in the
record specifications

The specification provides for the recording "... changed

name from.
The specification provides for the recording "... changed
description of the incident."
SF for these cases predicts the recording "... changed..."

It should be "Lack of attachments"

Information about the amendment of the assigned

person to the incident, there should be made a note in
the history of changes

Possibility of approving the hint with key enter

It should be "Lack of requirements"

It is possible to choose the lack of the version (empty

field)

The non-existent user is not being shown as the

manager of the project

The user should be informed of the impossibility of the

tie-up to the database.
The user should be informed of the impossibility of the
tie-up to the database.

password field should be marked as required.

On page 12 in the table with field type should be "Text

Box"
In the view of users of the project after moving the cursor
on red icon an announcement, in which the typographical
error of the "user".

The specification is describing it: "the Component is

available only to the person with entitlements of the root
or the Administrator. For the remaining users the
bookmark is invisible ".

The specification is defining it: "for the ordinary user

bookmark Projects will not be visible until assigning this
user for the project. "

There should be information about the change of person

assigned rather than information about the change in the
status

The application will prevent Polish signs in the e-mail

address

According to the matrix of privilages the ordinary user is

supposed to have access only to the view of the screen
of the log-on
It should be "closed off (for lack of requirements)" or
closed off (lack of requirements)
According to the specification he should name himself, in
this component, the "User"
According to the specification he should name himself
this component "managing incidents"

According to the specification it should be: "root"

According to the specification, history should have the

following appearance:
a. Jan Kowalski changed status from Programming to
the Question.
b. Jan Kowalski changed the priority from Normal on
High.

Field "repeat the Password" they are highlighting red and

according to specification side 4 is returning information
about the mistake
Field "repeat the Password" they are highlighting red and
according to specification side 4 is returning information
about the mistake

Mistake: according to. of Documentation Max of 50 signs

Of faces 3 signs, required, acceptable field there are

only letters

A user who is assigned to the project can not edit any

incident

No editing capabilities for the user to whom the incident

is not assigned

Icon appears on the taskbar

A scroll bar appears

Announcement of the fact that one should emphasize

the option "new installation" if you are installing the mr
application for the first time buggy

An error message should appear, e.g. "the made login

name and/or the password are incorrect"
Both of users should be removed

The incident should open normally along with the

possibility of performing available actions for the given
user

According to documentation "every project has an

individual name in Mr Buggy (to 36 signs)."

The incident was not saved. Error message

Attachment
https://docs.google.com/file/d/0B2s0SkW27WWGaTlBajRnMzRwNjQ/edit?pli=1

https://docs.google.com/file/d/0B2s0SkW27WWGdF9yZHROVERTcVk/edit?pli=1

https://docs.google.com/file/d/0B2s0SkW27WWGd2l4Y2VyM245REU/edit?pli=1

https://docs.google.com/file/d/0B2s0SkW27WWGd2l4Y2VyM245REU/edit?pli=1

https://docs.google.com/file/d/0B2s0SkW27WWGbjg4RmE3N1FKaE0/edit?pli=1

https://docs.google.com/file/d/0B2s0SkW27WWGTGRkUWhKc0N3Wk0/edit?pli=1

https://docs.google.com/file/d/0B2s0SkW27WWGX2QzMTdWWG5YSlk/edit

https://docs.google.com/file/d/0B2s0SkW27WWGUC15cEFFc1BzVzQ/edit?pli=1
https://docs.google.com/file/d/0B2s0SkW27WWGNVFKQWdrcUxOQnc/edit?pli=1

https://docs.google.com/file/d/0B2s0SkW27WWGTExIYzRySWctWkE/edit

https://docs.google.com/file/d/0B2s0SkW27WWGOGlXNEJiZ3RYRTA/edit

https://docs.google.com/file/d/0B2s0SkW27WWGcER6UWM1bzVxd0U/edit
https://docs.google.com/file/d/0B2s0SkW27WWGUzV2dDk4ZTllMUk/edit

https://docs.google.com/file/d/0B2s0SkW27WWGbkZUZWlBTHJNbWc/edit
https://docs.google.com/file/d/0B2s0SkW27WWGczZ1WkJSeUpxU2c/edit
https://docs.google.com/file/d/0B2s0SkW27WWGQTlXUGxTM1B5aVk/edit
https://docs.google.com/file/d/0B2s0SkW27WWGX0ZuNFowMk9MU2M/edit
https://docs.google.com/file/d/0B2s0SkW27WWGcnBzU1FOLVNzVUk/edit
Reproducibility
Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Not reproducible

Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always

Always
Always

Always

Always

Always

Not reproducible

Always

Always

Always

Always

Appeard once

Always

Always

Always
Category
New user
Sorting results
Incidents
Incidents
Incidents
Adding superadminstrator account
Member list
Log on

Editing a user

Incidents

Incidents

Incidents

New user
Log on
Project

Project

Project

Project

Incidents

Incidents

Project

Project
Project
Adding superadminstrator account
Adding superadminstrator account
Project
Project
Options

Incidents
New user
Assigning users to a project
Assigning users to a project

Connecting with database

Connecting with database

Connecting with database

Adding superadminstrator account

Incidents

Incidents

Editing a user

Sorting results

Assigning users to a project

Assigning users to a project

Projects
Projects

Editing a user
Projects
Incidents
Incidents
First run
Connecting with database
Users
Adding superadminstrator account

Incidents

Incidents

Creating user

Users

Incidents

Incidents

Project
Project

Project management

Incidents

Incidents

Users

Users

Projects
Projects
Projects
Incidents

Adding superadminstrator account

Incidents
Incidents
Specyfication
Specyfication
Specyfication
Incidents

Editing a user

Incidents

Incidents
Incidents
Incidents

Other
Users

Incidents
Incidents

Incidents

Incidents
Incidents
Projects

Incidents

Incidents

Users

Connecting with database

Connecting with database

Specyfication
Projects
Specyfication

Specyfication

Incidents
Users

Users
Incidents
Specyfication
Specyfication
Specyfication
Specyfication

Creating user
Creating user

Adding superadminstrator account

Incidents

Specyfication

Loging window

Incidents
Connecting with database
Connecting with database
Users
Incidents
Projects

Incidents

Sorting results