initial POC

[avdd]

Create initial proof of concept

• redirect / to /home
• serve skeleton html with inline css/js
• serve Home component
• serve bundle css
• serve app js
• success: selenium can see loaded home component

plan at #4 (comment)

[avdd]

status: figuring my way around selenium and its interaction with lazy loaded JS

[avdd]

will most likely proceed with ES modules as they can run without modification in the browser and node, and we can deal with js loading performance later.

also, what is a good approach to starting and stopping the server and browser processes per test? starting firefox is slooow

[avdd]

OK here is the plan.

• start server with environment SELENIUM_TEST=1
• server sets cookie selenium-test=1
• skeleton JS check cookie
• if cookie missing, call StartLoading()
• selenium test setup calls StartLoading()
• call LoadingProgress() for each step below
• StartLoading() adds <script> reference to app.js
• app.js fetches app.css and adds <style>
• app.js calls App.init()
• App.init fetches screen/home
• call initComponents()
• call FinishLoading()
• selenium test checks for presence of Home

further tweaks/refactoring:

• start server and browser once only, and clean up between tests
• separate the bootstrapping test above from subsequent TestCases
• use overlay with high z-index for loading message, reveal with fade

TODO:

• refactor JS components
• JS testing support using node
• generate JS component registry boilerplate
• separate python unit/integration/functional testing
• create TODOs for POC next steps

[avdd]

also, what is a good approach to starting and stopping the server and browser processes per test? starting firefox is slooow

done: use class-level setup

[avdd]

Calling this done. Further work to be chunked into issues