em-t-shells / testing_planetarium

JWA Foundation Project

The Planetarium is a web application designed by Revature Space Initiative for astronomers to track celestial bodies they discover in the night sky. Development work on the application is progressing, and the company wants to bring in testers to improve Quality Control to further improve product quality. Your job this Sprint is to perform manual testing on the application with two main goals: to look for defects in the product, and to give feedback on the user experience working with the app.

Project Focus

• Jira
• Manual Testing
• Test Case Creation
• Test Reporting
• System Testing
• Acceptance Testing

Software Requirements 

• Users should have unique usernames
• Usernames and passwords should not be longer than 30 characters
• Planet and Moon names should not have more than 30 characters
• Planets and moons should have unique names
• Planets should be “owned” by the user that added it to the Planetarium
• Moons should be “owned” by the Planet the User adding the moon associated it with
• Planets and Moons should allow adding an associated image, but an image should not be required for the data to be added to the database

Use Cases

• Users should be able to open a new User account with the Planetarium
• Users should be able to securely access their account
• Users should be able to see planets and moons added to the Planetarium
• Users should be able to add new Planets to the Planetarium
• Users should be able to remove Planets from the Planetarium
• Users should be able to add Moons to the Planetarium associated with a Planet
• Users should be able to remove Moons from the Planetarium

Testing Requirements

• All Test Reporting should be done in Jira
• All Use Cases require a minimum of one positive test
• All Use Cases with associated software requirements require negative testing to verify requirements are met
• All Use Cases with Software Requirements that limit data input require Boundary Analysis Testing
• All Use Cases with Software Requirements that limit data visibility require Error Guess Testing
• All Use Cases with Software Requirements that limit data interaction require Error Guess Testing
• All tests that fail should be logged in a Defect Report inside of Jira
• Acceptance testing for the user experience should answer the following questions in detail:
  • Is the intended use of the service intuitive?
  • Is the service easy to use?
  • Does the service inspire confidence?
  • Is the service pleasing to look at?

MVP Requirements

• Test Cases are created for Use Cases
• Test Cases are saved in Jira
• Manual Tests are complete
• Test Results are saved in Jira
• Defect Reports are created for each failed test
• Defect Reports are saved in Jira

Suggested Stretch Goals

• perform extra Error Guess Testing
• perform Non-Functional System testing

Setup Requirements

• an environment variable called "PLANETARIUM" needs to be set with the JDBC url for the planetarium database
  • SQLite3 is used by the application
• a database needs to be created and set up for the planetarium to work properly. Use the setup-reset.sql file to create the database at the same location as your "PLANETARIUM" environment variable
• start the application with the command java -jar path/to/Planetarium-1.0-shaded.jar