Skip to content

[SIGMON-149] Analyse notebook content in the tests

Aleksandra Mnich requested to merge SIGMON-149_test_notebook_content into dev

Context

What was done

  • the output of the notebook is 'analysed' and compared with the reference one,
  • setting up the connection to Spark3 apparently we were already using Spark3 before (even though the script says that it should be spark2 by default).

TODO

QA

  • no sonar
  • code was not unit tested because it's a CI task and end-to-end tests were updated
  • acceptance tests were not written, because it's a CI task and end-to-end tests were updated

Review objectives

  • assessment of code functionality
  • assessment of code quality
  • identifying potential refactorings / logic common to other projects
  • knowledge sharing
Edited by Aleksandra Mnich

Merge request reports