Skip to content

Latest commit

 

History

History
55 lines (29 loc) · 3.06 KB

README_TASKS.md

File metadata and controls

55 lines (29 loc) · 3.06 KB

Your turn now!

1) Complete implementing an API for the simulator in your ITU-MiniTwit.

Next week, we will start a simulator that will run until the end of this course. It will simulate users using your micro-blogging platform.

You can find the specification for the simulator API in API_Spec/minitwit_sim_api.py (session_03). OBS: your applications have to:

  • provide the same end points (on different hosts of course and potentially different ports),
  • ingest the same HTTP requests, i.e., GETs and POSTs as specified with the same parameters and payloads as provided,
  • provide at least the same HTTP status codes in response as specified.

The API_Spec/minitwit_sim_api.py depends on your refactored minitwit.py from last weeks' homework.

A corresponding test (API_Spec/minitwit_sim_api_test.py) illustrates how the simulator requests will be formed. You can inspect it and run it via pytest minitwit_sim_api_test.py.

Next to the unit test, there is a small program with some more test data, which is similar to the simulator program that will run against your systems. It is located in API Spec/minitwit_simulator.py and can be run via:

$ python minitwit_simulator.py http://localhost:5001

where the argument http://localhost:5001 has to be replaced with the URL of where you simulator API is running. In case this simulator test does not log any errors, you should be all fine for next week. If errors are logged, you have to likely fix the corresponding issue either in your implementation of the simulator API or in the implementation of your version of ITU-MiniTwit.

2) Creating a CI/CD setup for your ITU-MiniTwit.

Until next week, create a CI/CD setup for your ITU-MiniTwit development.

  • You can freely choose your CI/CD system. BSc students are likely best served by adapting the example from the scenario from Today's Exercises. But in essence everybody can choose freely.
  • OBS MSc students: Remember to log and provide good arguments for the choice of CI/CD system, i.e., why do you choose your solution instead of any other?
  • For now, you choose freely if you want to go for continuous delivery or continuous deployment.
  • Let your build pipeline contain not only building your application but also execution of your test suite and other appropriate build stages.

From now on create the (at least weekly) releases on GitHub automatically. Release that version of your ITU-MiniTwit that is in production.

3) Continue refactoring of your ITU-MiniTwit.

Continue refactoring of your version of ITU-MiniTwit with the features of your liking.