Improving the test suite

[marimeireles]

What kind of tests do we want?

End-to-end tests and Unit tests. We should start with unit tests and then end-to-end tests. For the Python side and JS side, both PyScript APIs directly and using our examples to test user experiences with playwright.

• Check the DOM and the possible interactions (playwright)

  • We want to write individual tests for each individual examples
    • We want to try to do what an user would do
  • it's a good time to define which examples we want to keep in the repository and which should go to the collective

• Check the console for messages (JS offers that, Python might)

• We need to test the actual library (pytest for the python side, we should use plain TS for the TS side)

  • We want unit tests for each of the functions on the python side, on the TS side we should check what the objects are doing and then write unit test for them

Some things that can help us in the process of writing good code 🙂 :

• We might want to use the POM(page object model) design pattern
• @keshavneupane kindly shared a minimal playwright example for use to base ourselves on
• Anaconda UI offers a good example. This is not available to the wide public.
• Another recomendation blogpost from Keshav about playwright

Tests in depth

• Improve current test system by checking the logs on the console #612
• Create infrastructure and write the first DOM check test #613
• Create infrastructure and write the first interactive example #614
• Every new feature should have a test #615
• Create infrastructure and write the first JS unit test #616
• Create infrastructure and write the first Python unit test #617
• Create boilerplate for running TS tests #660

@madhur-tandon @antocuni @fpliger @ntoll