You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current integration test suite is large and comprehensive but is only runnable manually. OSS folks who open PRs can't run them and it's a big process for us to run them manually. Make it possible to trigger integration tests.
For integration tests to run:
ironcore-id needs to be running locally with its postgres DB
project, assertion key, and segment info that is valid on that ironcore-id instance needs to be in integration/projects/project.json (can probably be canned DB scripts)
https certs for dev1.scrambledbits.org need to be up to date (automating this is the hardest part)
yarn start needs to run the integration app
yarn nightwatch can then run the suite, though that requires chrome to be installed so chromedriver works
A possible workaround to the https certs issue would be to make the integration app not require https, but the scope of that is unknown at the time of writing this ticket.
The text was updated successfully, but these errors were encountered:
Possibly start chrome in a mode that accepts untrusted certs. If that wouldn't work, could potentially install a CA and generate certs when running the tests.
Why will it still be hard? No one knows, but they know it will be.
Our current integration test suite is large and comprehensive but is only runnable manually. OSS folks who open PRs can't run them and it's a big process for us to run them manually. Make it possible to trigger integration tests.
For integration tests to run:
ironcore-id
needs to be running locally with its postgres DBironcore-id
instance needs to be inintegration/projects/project.json
(can probably be canned DB scripts)dev1.scrambledbits.org
need to be up to date (automating this is the hardest part)yarn start
needs to run the integration appyarn nightwatch
can then run the suite, though that requireschrome
to be installed sochromedriver
worksA possible workaround to the https certs issue would be to make the integration app not require https, but the scope of that is unknown at the time of writing this ticket.
The text was updated successfully, but these errors were encountered: