Scribd
Upload
29 views3 pages

STE Bug Challenge - Web Platforms

Uploaded by

K-yfan Hernandez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
29 views3 pages

STE Bug Challenge - Web Platforms

Uploaded by

K-yfan Hernandez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

STE Assessment- Bug Challenge

Bug-Finding Challenge:

At Paylocity, the highest priority of the software tester is to find bugs before the end
user does. This challenge is designed to have you demonstrate your bug-finding
ability in both the API the UI of an application.

Instructions:

For the sample Benefits Dashboard application, please do the following:

Find as many bugs/defects/flaws as you can in the UI and the API and create a
report. This report should be similar to what you would present to the developer of
the application, with the type of detail that you would normally include.

Submission:

Your submission should include the following:

• A bug report for all the API bugs you found, with details and steps to reproduce
• A bug report for all the UI bugs you found, with details and steps to reproduce

GitHub is the preferred method of sharing your submission

URL and Login info:

URL: https://wmxrwq14uc.execute-api.us-east-
1.amazonaws.com/Prod/Account/Login

Your username, password, and auth token for API testing will be provided to you in a
separate email.

API Documentation:

The API documentation can be found at the below link:

https://documenter.getpostman.com/view/2314100/SWTEbbi6

Note that you will need to use your assigned auth token in the header of your requests
in order to access the API.
For example: Key: Authorization; Value: Basic <authToken>
Postman users can use the “Run in Postman” button to migrate the requests to their
Postman account. If you prefer Swagger documentation, you can find it
here: https://wmxrwq14uc.execute-api.us-east-
1.amazonaws.com/Prod/swagger/v1/swagger.json

The Application:

One of the critical functions that we provide for our clients is the ability to pay for their
employees’ benefits packages. A portion of these costs are deducted from their
paycheck, and we handle that deduction. This is a small, buggy, sample application
that allows the user (an employer) to add, edit, and delete employees and their
dependents.

Assumptions:

• All employees are paid $2000 per paycheck before deductions


• There are 26 paychecks in a year
• The cost of benefits is $1000/year for each employee
• Each dependent incurs a cost of $500/year

User Story:

As an Employer, I want to input my employee data so that I can get a preview of


benefit costs.

Acceptance Criteria

Scenario 1: Add Employee

GIVEN an Employer
AND I am on the Benefits Dashboard page
WHEN I select Add Employee
THEN I should be able to enter employee details
AND the employee should save
AND I should see the employee in the table
AND the benefit cost calculations are correct

Scenario 2: Edit Employee

GIVEN an Employer
AND I am on the Benefits Dashboard page
WHEN I select the Action Edit
THEN I can edit employee details
AND the data should change in the table

Scenario 3: Delete Employee

GIVEN an Employer
AND I am on the Benefits Dashboard page
WHEN I click the Action X
THEN the employee should be deleted

You might also like