Hi everyone,
For context: Currently at work my project is undergoing an architecture rewrite, currently the content for the pages are being injected through a chain of gulp tasks (at the time it was written I don’t believe webpack was being used at enterprise level) at build time, the content was located in a cms.
The content on our pages are completely static outside of servicing requests.
My idea is to move away from the gulp tasks injecting content and move towards building an API that would run at build time in the pipeline and generate the static pages.
The reasoning behind my thought is because we have regulatory requirements on certain pages so there is a requirement to validate the contents accuracy. Currently we are doing this with e2e tests through selenium grid (which is extremely unstable and takes an extremely long to run). I would test the response from the API to ensure it’s accuracy at an integration testing level and remove all the junk e2e tests we have on our release pipeline.
What are your thoughts on this approach, is there a better way, is this way just flat out wrong? I would love to hear everyone’s opinions 😊
submitted by /u/TabisCAD
[link] [comments]