Trinitex - Task
Trinitex - Task
http://test.trinetix.net/task/
Describe test scenarios of the web page (in general, without excessive details)
Test the page in any browser of your choice. Describe bugs freely (following the bug description
guidelines is not needed; however, bugs have to be comprehensible to an imaginary developer whose
task will be to fix them).
Do not pay attention to the mistakes in text.
Question 1 - Read the specification and identify any aspect that is unclear or risky.
From this, provide a written list of questions you would ask the Business Analyst to clarify this
spec before development begins.
e.g. "What should happen if the two passwords entered on the "Edit Password" screen don't match?"
Question 2 - Imagine that the Business Analyst is about to leave on a month holiday, and the feature
will be implemented and shipped while s/he is away. S/he is in a hurry and has to leave work to catch
her flight in 10 minutes.
From your list, choose 3-5 questions that you believe are the most important for her/him to
answer before s/he leaves.
Justify your choices. Why did you select those questions? What answers do you expect to
receive? How would you expect the answers to affect the development work?
You may assume that you are working in an Agile team, and that developers have the power to
make independent implementation choices for anything that remains unclarified.
Hints...
For this exercise, focus on problems with ambiguity - that is, places where the specification
doesn't make it clear how the feature should behave. Some categories of ambiguity issues are:
1. Dangling-Else: i.e. "The system will do operation X when A happens". What if A doesn't
happen? Is A the only possible thing that could happen?
2. Ambiguity of Reference: i.e. "If condition A is true, the default behaviour will kick in". What's
the "default behavior"? Is it well defined?
3. Ambiguity of Scope: i.e. "For all other cases, the system will ignore the input". Is there a finite
set of "other cases"? What makes us so confident about this?
Specification
From this, provide a written list of questions you would ask the Business Analyst to clarify this
spec before development begins.
e.g. "What should happen if the two passwords entered on the "Edit Password" screen don't match?"
Specification
1. "What should happen if the two passwords entered on the "Edit Password" screen don't match?"
2. What are minimal and maximum lengths of passwords {what range of chars number does it
include?} [from.....to]? What should happen if user inputs too shot password? Too long password? Is it
supposed to check the length of password input and its reliability?
3. What symbols are admissible and non-admissible for passwords? What kind of message should
return if your password include non-admissible symbols?
Minimum length: 8
Minimum number of lowercase characters: 1
Minimum number of uppercase characters: 2
Minimum number of digits: 1
Minimum number of different classes of characters: 2
Forbidden characters: @%\
4. What should happen if I try to copy& paste too long file in password field?
5. In which way should I hide password in password fields (e.g dots, stars and so on)?
6. Is it possible to copy&paste hidden password from “Password field” to “Confirm password” field or
I should reenter it again?
9. What should happen if user press “Save” button in “Change password” form and” Password” and
“Confirm Password” fields remain empty?
10. What should happen if user press “Save” button in “Change password” form and ” Password” field
remains empty but “Confirm Password” include password and vice versa?
11. Details about “Change password” form (Fonts, button's size, field's length, right, left top, bottom
alignment, background, etc).
12. What the user's/admin algorithm if user/admin has forgotten his/her own password? Should field
with old password be here in order to confirm your identity?
12.1. What a mechanism of changing password if user is going to use previous password as a new
password? If there is no such mechanism then what is the main idea of this form Change password?
Does it make sense? Should title “Password” be changed to title “New Password” in ”Change
password” form (page) ?
12.2. How many attempts does user have if passwords don't match?, Is there any mechanism of user
blocking after a few failed attempts to prevent non-authorized access?
13. In which way user's password can be restored? Any mechanism to restore/reset password for
user/admin?
15. How many projects admin and/or user is (are) able to create?
16. Edit Details: What should happen If in “Edit details” user input invalid email?
17. Why mandatory fields are not marked in “Edit details” form? What are mandatory fields there?
18. Edit Details: What should happen if user press “Save” button and all (three) field remain empty?
19. Edit Details: What should happen if user press “Save” button User Name and Full Name field
remain empty? Or any single field remains empty?
20. Edit Details: What are minimal and maximum lengths of Username, Full Name, Email {what
range of chars number does it include?}
21. Edit Details: What symbols are admissible and non-admissible for Username, Full name, Email?
(special chars, only numbers, signs of punctuation, e.g @#$%^&;.?,>|\/№"!()_{}[<~,). Please define
format here?
22. Edit Details: Is it possible to have Upper Case, Lower case, Mixed in User Name, Full Name?
23. Edit Details: What should happen if user press “Cancel” button? Go to My profile page or reset
input data?
24. Edit Details: In which way will user be able to download, edit, delete his/her own Avatar picture
because we can see it on “My Profile page”?
25. Which format of graphic data should user use, maximum size?
27. What should happen if user/admin press link log out? How should this page look like after log out?
Should be there confirmation of your logout/or not?
Test
http://test.trinetix.net/task/
Describe test scenarios of the web page (in general, without excessive details)
Test the page in any browser of your choice. Describe bugs freely (following the bug description
guidelines is not needed; however, bugs have to be comprehensible to an imaginary developer
whose task will be to fix them).
Do not pay attention to the mistakes in text.
Issue#1
Remained empty “Email” field returns wrong message (negative scenario)
Priority: Medium
Steps to reproduce:
1. go to http://test.trinetix.net/task/
3. Click “Subscribe”
AR: Remained empty “Email” field returns wrong message (Please see screenshot)
Issue #2 There is no email confirmation after valid email input and subscribe button pressed
Priority: High
Steps to reproduce:
1. go to http://test.trinetix.net/task/
3. Click “Subscribe”
4. Check Inbox
AR: There is no email confirmation after valid email input and subscribe button pressed (Please see
screenshot)
Issue#3 Links to social networks do not operate at all, after pressing on them, User goes to the top of
the page
Issue#4 Link Google+ (social network) is not highlighted when user hovers mouse arrow (Please see
screenshot)
Issue#5 Localization is not implemented (User should be able to choose native language), but IMO it
depends on business orientation of this web page
Issue#6 Buttons “Get in touch” and “GET THE APP” at the top of the web page do not operate at all
Issue#7 Button “GET THE APP” at the bottom of the web page forwards user to the wrong
(nonexistent) page
Issue#8 Banners with IPhone are cut otherwise UI designers have other idea.
Issue#9 Links with iPhone images return the same result (the same image)
Issue#10 The 3d link with iPhone if count from the left side is not active when user hovers mouse
arrow on it, so it should change as three ones. And we should see zoom device here
Issue#11 From UI designer point of view Button “Get in touch” should have more attractive
background (probably blue background and yellow sign in it or vise versa) and visible location.
Issue#12 Banner with IPhone and background tower buildings should be gummed with the bottom
banner with the same background
2. Apply test design techniques to check positive and negative scenarios (use invalid and valid email
address to subscribe)
3. check if "email" field can contain special chars or only special chars, numbers @#$%^&;.?,>|\/№"!
()_{}[<~
4. Check if “email” field can contain Upper case, lower case, Mixed with this char @ +special chars,
numbers at the beginning, in the middle and at the end of email address
5. Error – guessing technique: if email field can contain too long string more than 100 KB
Question 2 - Imagine that the Business Analyst is about to leave on a month holiday, and the feature
will be implemented and shipped while s/he is away. S/he is in a hurry and has to leave work to catch
her flight in 10 minutes.
From your list, choose 3-5 questions that you believe are the most important for her/him
to answer before s/he leaves.
Justify your choices. Why did you select those questions? What answers do you expect to
receive? How would you expect the answers to affect the development work?
You may assume that you are working in an Agile team, and that developers have the
power to make independent implementation choices for anything that remains unclarified.
Hints...
For this exercise, focus on problems with ambiguity - that is, places where the specification
doesn't make it clear how the feature should behave. Some categories of ambiguity issues are:
4. Dangling-Else: i.e. "The system will do operation X when A happens". What if A doesn't
happen? Is A the only possible thing that could happen?
5. Ambiguity of Reference: i.e. "If condition A is true, the default behaviour will kick in". What's
the "default behavior"? Is it well defined?
6. Ambiguity of Scope: i.e. "For all other cases, the system will ignore the input". Is there a finite
set of "other cases"? What makes us so confident about this?
From your list, choose 3-5 questions that you believe are the most important for her/him
to answer before s/he leaves.
1. What are minimal and maximum lengths of passwords {what range of chars number does it
include?} [from.....to]? What should happen if user inputs too shot password? Too long password? Is it
supposed to check the length of password input and its reliability?
2. What symbols are admissible and non-admissible for passwords? What kind of message should
return if your password include non-admissible symbols?
Example: Your password must conform to the following constraints:
Minimum length: 8
Minimum number of lowercase characters: 1
Minimum number of uppercase characters: 2
Minimum number of digits: 1
Minimum number of different classes of characters: 2
Forbidden characters: @%\
12. What the user's/admin algorithm if user/admin has forgotten his/her own password? Should field
with old password be here in order to confirm your identity?
12.1. What a mechanism of changing password if user is going to use previous password as a new
password? If there is no such mechanism then what is the main idea of this form Change password?
Does it make sense? Should title “Password” be changed to title “New Password” in”Change
password” form (page)?
12.2. How many attempts does user have if passwords don't match? Is there any mechanism of user
blocking after a few failed attempts to prevent non-authorized access?
13. In which way user's password can be restored? Any mechanism to restore/reset password for
user/admin?
Justify your choices. Why did you select those questions? What answers do you expect to
receive? How would you expect the answers to affect the development work?
From security point of view, password should be effective, reliable, not to be hacked with
modern tools until secured info has incredible value and thus I pay my attention on that issue.
Let’s imagine: We have form illustrated below, culprit who got your password to PC go to you
profile as you had ticked “Remember my password” due to this scenario culprit will be able to
change password as he wants, moreover he will have full access to your private data which can
be changed, modified, deleted and so on. I’d make a hazard that BA will agree with me that we
need to do this system more secure and he/she will accept my idea to change this page design
and logic of this secure mechanism.
Next issue I’d like to rise about detailed requirements to the length of password and symbols it
should contain as this is crucial factor for the stability of this password
I expect to receive next answer.
Example:
This approach will do your profile more secure and stable as your profile with 100% possibility
contain very important info and personal data
3 You may assume that you are working in an Agile team, and that developers have the power to
make independent implementation choices for anything that remains unclarified
1. What should happen if I try to copy& paste too long file in password field? (Warning message of
your choice should appear in this case which is able to edit easily during development)
2. In which way should I hide password in password fields (e.g dots, stars and so on)? (It does not
make sense in which way developers will hide your password in “Password” field the main condition it
should be hidden)
3. Edit Details: What should happen if user press “Cancel” button? Go to My profile page or reset
input data? (Use previous experience of almost the same functionality If user presses “Cancel button”
he will quit from this form (page))
4. Edit Details: In which way will user be able to download, edit, delete his/her own Avatar picture
because we can see it on “My Profile page”? (Implementation if user presses on avatar then new page
opens with editing option of your avatar Use previous experience of almost the same functionality)
5. Which format of graphic data should user use, maximum size? (Use previous experience of almost
the same functionality, e.g jpeg, etc until to 1 MB)
6. Edit Details: What should happen If in “Edit details” user input invalid email?
7. Why mandatory fields are not marked in “Edit details” form? What are mandatory fields there?
(Probably email, User name, Full Name)
8. Edit Details: What should happen if user press “Save” button and all (three) field remain empty?
(Warning message should be implemented)
9. Edit Details: What should happen if user press “Save” button User Name and Full Name field
remain empty? Or any single field remains empty? (Warning message should be implemented)
10. Edit Details: What should happen If in “Edit details” user input invalid email? (Checking
mechanism of your email include all necessary constraints)
11. Why mandatory fields are not marked in “Edit details” form? What are mandatory fields there?