What is testing?
Process of evaluating a product
To verify that it functions as intended and is free from any defects
Why is testing important?
Ensure developers that they are releasing a high quality product
Helps the product meet customer satisfaction
Identifies vulnerabilities in a product
Cost-effective in the long run for companies
Types of testing at uTest
Functional
Usability
Localization
Security
Payment
On-site
-------------------------
What is a screenshot
An image of the data displayed on the screen of a computer or mobile device
Testers need to attach screenshots in their bug report
Let's take a look at the rules a screenshot must follow
Screenshot rules
Always highlight or mark up the screenshot to clearly show the bug
Always remember to save the screenshots in either .jpg or .png format
Avoid using a mouse or hand drawing tool to highlight your screenshot
Make sure that your screenshot includes the entire device screen(including the
browser url bar when testing a website)
Hide or close the browser tabs which are not related to the testing website
Every screenshot you take must be in the upright orientation
----------------------------
What is an Invitation?
An oppurtunity for a tester to participate in a test cycle
uTest(Example) sends you an invitation
Through an email and a push notification from the uTest mobile app
Make a decision
Do not rush and accept the cycle invitation
Always read the overview before accepting the cycle invitation
Decide whether to accept or decline the invitation
------------------------------------------
Completing test cases on time
Only claim a slot or a test case when you have time to complete it
Always finish the test case within the specified time
Unclaim the test case if you cannot complete within the specified time
Not completin the test case on time will affect your rating negatively
Do not keep your test case idle
Start working on the test case as soon as possible
This allows time if there are technical difficulties
Or for communication and clarification
Always use the correct environment
Claim a slot or a test case only if you have a matching environment for it
Choose the correct environment while claiming a slot
Execute the test case only on the specified environment
Test cases will be rejected if you execute it on an incorrect environment
Execution
Carry out each test case step completely and provide the required attachments
Use comments if you want to mention something regarding a step
Make sure every failed step has a bug associated with it
Other best practices
Always respond to the info request messages quickly
Do not attach very large attachments, compress them before attaching
Always submit the test case after completing it by clicking on "Submit Results"
Provide accurate time spent information
--------------------------------
What is a bug or an issue?
An error, flaw or fault in a product
That causes it to produce an incorrect or unexpected result
Types of bugs
Functional
Visual
Content
Performance
Crash
----------
(Examples)
----------
Functional
Workflow failures
Where something in the test application did not work as it was designed to
Produce an unexpected or illogical application behavior
Visual
Affect the layout of a page
Where some elements such as images may be missing
Content
Affect the text of a page
Such as spelling, grammar and localization errors
Performance
Result in features taking longer to load than expected
Overall slow navigation within the application
Crash
When an application quits or
Closes unexpectedly while in use
----------------------------------
What is a Bug Report?
Written summary of a bug
This contains all the information required to understand, reproduce and fix the bug
A bug report contains several fields which need to be filled by the tester properly
Issue Title
A short description of the bug
Testers should follow the title format as specified in the cycle overview
Isseu Type
Where you select the type of bug you are reporting
We already discussed the different types of bugs in previous tracks
Frequency
Used to specify how many times the issue can be reproduced
Such as everytime or just sometimes
Priority
Used to specify the severity of the bug
Environment
Used to specify in which device the bug is produced
Make sure to select correct device, browser and OS combination
(example)
Windows 10-Chrome-Wi-Fi
Samsung Galaxy Note 10-Android 10-4G Netwrok
iPhone 11-iOS 13.3.1-5G Network
Actions Performed
Where you will write all the actions you performed to produce the bug
Make sure to use numbered steps starting from opening the site or app
Expected Results
Describe exactly what the user would expect to happen
When carrying out the steps described in the actions performed
Actual Results
Describe exactly what does happen
When the user carries out the steps in the actions performed
Error Messages
Used to specify any error message you may have received
Additional Environment Info
Used to provide any additional information regardiing the bug
Attachments
Where you will upload all the required attachments
Such as screenshots, screen recordings or logs
