Web Testing Cases

Functionality Testing

This is used to check if the product is as per the specifications intended for it as well as the functional requirements charted out for it in developmental documentation.

● Testing fields and forms accept correct format / length data
Register form - passed
Create a Poll - failed(create choices do not validate the length of input)

● Verifying validation errors are presented to a user where invalid data is entered
Response form - passed
Register form - failed
Create a poll form - passed

● Ensure both internal and external links on a site function correctly
passed

● Verifying default values are being populated
Create a poll form - passed

● Successful flow through of basic flows in end-to-end business scenarios
passed (please see UAT testing results under PBIs)

● Verifying validation errors are presented when the business scenarios are executed incorrectly
passed

● Data flow across integration systems
passed

Usability Testing

This is used to check if the application is consistent in look, feel, terminology and workflow.
● Consistency of UI, including colours / fonts / layout
passed
● Consistency of field names / formatting
passed
● Consistency of validation error message text and display formatting
failed (User registration form does not show why validation has failed)
● Ensuring no grammatical or spelling errors are present in the application
passed
● Business workflow is intuitive
passed

Interface Testing

This is used to check that queries made between the application, web and database layers return correct data when queries, and that validation errors are handled correctly.
● Database errors are not shown to the end user
passed

● Application requests are handing correctly without being denied by the server
passed

● Queries sent to the database return expected results
passed

# Compatibility Testing
This is used to check that a web application displays correctly across different devices, or at different resolutions. This is using either done based on either market share, or as per requirements.
● Testing across different web browsers
Chrome - passed
IE - failed (will not fix)
Safari - failed (will not fix)
Firefox - passed
Chrome - passed

● Testing certain combinations of operations systems & browsers
Windows - passed
Mac - passed
Linux - Not tested

Performance Testing

This is used to check a web application works under load. This encompasses load testing, stress testing and responsiveness.

A python script for creating and querying large amount of poll data and loaded to the running web as a stress testing. We did not see any abnormal results.

● Verifying response times are acceptable when executing large queries
Not tested
● Verifying system responsiveness when loading data or image heavy page elements
Not tested
● Caching is implemented effectively
Not tested
● Verifying the system responsiveness when large numbers of users are present on the system, or are executing the same functions simultaneously
Not tested

Security Testing

This is used to check the system contains restrictions for user types, and protects user sessions and data.
● Verifying access to unauthorised pages is not permitted
Front End Web - passed
API - failed (access is always denied with @token_auth.login_required)
● Ensuring that passwords are stored encrypted
passed