QA (public) » openQA Project (public)

Motivation¶

In openQA we have some JavaScript code with no good unit tests and multiple outdated dependencies. Before doing the hard job of implementing unit tests or significantly updating our stack we should evaluate what's new as of year 2024 and decide if we should use new approaches in some cases.

Acceptance Criteria¶

• AC1: It is known if one or multiple frameworks would simplify our code and/or unit tests
• AC2: Follow-up task have been reported

Suggestions¶

• Look into alpine.js and try to apply it for openQA
• Look into vanilla CSS nesting and try in a draft openQA pull request, potentially also qem-dashboard
• Look into native JavaScript modules
• Might be worth looking at (perhaps somewhere in a different epic) is openAPI, gRPC (or a combination, taking into account we're heavy users of WebSockets though), Open API uses a lot of yaml :D so of course there are tradeoffs, but would help with proper API versioning. Especially looking at decoupling os-autoinst's command server with the intention of being able to generate native testapi bindings for other languages

Out of scope¶

• Complete transformation of existing features using new tooling. Just identify and report as separate tickets
• For htmx in particular follow #156055
• For replacing jQuery.ajax with fetch see #166310