Summary: In this final sprint in your first project, you will use
all the data that you have downloaded and display it to the users in
a useful manner
We will continue to use the same version control, continuous integration tools and programming language requirements that we put together for parts one - three.
You have come a fair ways in creating a
project that is useful and built in parts. This last sprint will
finish it up and add lots of useful features. You have more time to
be self directed, but the extra time is important because you will
need it.This sprint takes more time and will be worth more credit, this one sprint will be worth about two of
the previous sprints
Due: Sunday March 6th at 11:59pm
(officially Spring break starts on Monday the 7th)
Now create a GUI to allow the user to interact with your project more naturally.
The steps below are numbered only to make it easier to read. If you find it easier to work on the deliverables in a different order please do so.
NOTE: I've been very careful not to tell you how to display it, only what to display. use your creativity to show all of this information in a useful format.
Add additional tests to your test suite. You should include tests to make sure your data analysis functions work properly (ordered data, and counts of the positive and negative movers at least.)
make sure all of the previous tests still work.
write tests for the top250/most popular crossovers.
For the GUI, either use a tool like selenium (which you will have to learn on your own), or write a detailed manual test plan (with pictures) to explain what should happen when your graphical elements are invoked. There is a lot of disagreement in the industry about whether automated GUI tests are worthless or vitally important.
as before, update any github actions with dependency management and anything else you need to make the Continuous Integration continue to function.