Tests not passing

[jcody49]

I have gotten a lot of tests to pass. I also figured out the testing environment, and now I'm finally getting 200 codes and my test users are finally being created and authenticated correctly... however... now the opposite has been a problem--testing the apps redirects... for whatever reason, my app just can't the user redirected with the appropriate error message. This is the main issue for a lot of the tests, but there are also concerns with the tests that test the data being extracted and the charts that are rendered from that dataframe...

[jamesdwilson]

@jcody49 Please use a formal ticket structure and clearly state what is wrong and how to reproduce it.

Ticket Title: Redirect and Data Handling Issues in Testing Environment

Description: Encountering issues with user redirection and the display of appropriate error messages during testing. Also, concerns arise with data extraction and chart rendering from dataframes.

Steps to Reproduce:

1. User Creation and Authentication:
   • Run the relevant tests to confirm they pass with 200 status codes. Note: Check test logs for status codes to ensure successful user handling.
2. User Redirection and Error Messaging:
   • Execute tests that involve user redirection with error messaging. Note: Observe and note any deviations from expected redirection paths or missing/error messages.
3. Data Extraction and Chart Rendering:
   • Perform tests aimed at data extraction and chart rendering. Note: Verify the accuracy of extracted data and the integrity of rendered charts against expected outcomes.

Expected Results:

• Users are redirected as intended with relevant error messages.
• Data is accurately extracted, and charts are correctly rendered from dataframes.

Actual Results:

• Detail the actual results observed during testing, specifying any errors, incorrect data, or misrendered charts. Use logs and test outcomes to provide specific examples.

Environment:

• Specify the environment in which the testing is conducted, including OS, application version, and testing tools. This information is crucial for replicating the issues and understanding the context.

Additional Notes:

• Include any other observations or logs that could aid in diagnosing the issues. This could involve specific error codes, screenshots of failed tests, or patterns noticed during testing that could indicate a larger problem.