Skip to content

Test Plan and Results

Nick Clason edited this page Apr 14, 2022 · 3 revisions

Test Plan

The testing that will be conducted for our web application will be split into four separate components. These components include Account Authentication, Data Retrieval, Database, and Compatibility. The first component is Account Authentication; by conducting the tests in this area, we can verify that users are granted a functional and secure account service. Testing the Data Retrieval and Database areas of the web application will ensure that users are getting the correct corresponding data to their requests. Finally, the Compatibility of the application will be tested in order to assure users will be able to utilize this application across a variety of different browsers/devices/platforms, so that there will be a consistent user experience across all users.

Results

Test Description Results Notes
AA1 This test will ensure that a user can successfully register for a newly created account Pass -
AA2 This test will ensure that entering a user’s credentials will perform authentication successfully Pass -
AA3 This test will ensure that a user can successfully log out and the system performs the correct de-authentication process Pass -
AA4 This test will ensure that a user will be denied authentication to an account if attempting to log in with incorrect credentials Pass -
DR1 This test will ensure that a user can select a financial entity and its corresponding price history and information is retrieved from the database and displayed to the user Pass -
DR2 This test will ensure that when a user navigates to their portfolio within the application, their assets’ corresponding data for prices and amounts display successfully Pass -
DR3 This test will ensure that a user can request the model’s price projection and a generated price outlook will be returned to the user Pass -
DB1 This test will ensure that the database query when logging in returns the correct response Pass Tested by sending requests directly to backend without interfacing with frontend
DB2 This test will ensure that the database query for registering a user returns the correct response and commits the user to the database Pass Tested by sending requests directly to backend without interfacing with frontend
C1 This test will ensure that a user can access the web application successfully across different browsers and platforms, such as Chrome and Firefox on PC, Mac, and Mobile Pass/Fail Functions properly on desktop browsers, mobile browsers need more work to function 100% correctly

Clone this wiki locally