4 Commits (c2070877b66accb9bcdefcd269388d8197ed02f2)

Author	SHA1	Message	Date
George Gevoian	a294eefdff	(core) Update HomeIntro.ts to check for either login page ... Summary: The "Sign In" button can either redirect you to the Cognito login page or the Grist sign-up page, depending on whether you've logged in before. Since the HomeIntro tests can either be run as part of a full deployment test suite, or individually, the test could redirect you to both types of login pages. Test Plan: N/A (fixing test) Reviewers: paulfitz Reviewed By: paulfitz Subscribers: paulfitz Differential Revision: https://phab.getgrist.com/D3291	3 years ago
George Gevoian	ac910389bc	(core) Make login URL regexes more specific ... Summary: This should resolve some staging test failures. The previous regexes weren't quite specific enough, so random parts of a URL that had traces of the real login URLs were causing isOnLoginPage() and isOnGristLoginPage() to return true instead of false. Test Plan: N/A (fixing tests) Reviewers: paulfitz Reviewed By: paulfitz Differential Revision: https://phab.getgrist.com/D3283	3 years ago
Dmitry S	9c57b565b2	(core) Fix deployment tests. ... Summary: - Skip welcome questions in HomeIntro - Make Funnel test less flaky, and increase its timeout Test Plan: Both tests pass staging_deployment when run locally Reviewers: georgegevoian Reviewed By: georgegevoian Differential Revision: https://phab.getgrist.com/D3218	3 years ago
Paul Fitzpatrick	d99db8d016	(core) move more tests to grist-core ... Summary: * Tie build and run-time docker base images to a consistent version (buster) * Extend the test login system activated by GRIST_TEST_LOGIN to ease porting tests that currently rely on cognito (many) * Make org resets work in absence of billing endpoints * When in-memory session caches are used, add missing invalidation steps * Pass org information through sign-ups/sign-ins more carefully * For CORS, explicitly trust GRIST_HOST origin when set * Move some fixtures and tests to core, focussing on tests that cover existing failures or are in the set of tests run on deployments * Retain regular `test` target to run the test suite directly, without docker * Add a `test:smoke` target to run a single simple test without `GRIST_TEST_LOGIN` activated * Add a `test:docker` target to run the tests against a grist-core docker image - since tests rely on certain fixture teams/docs, added `TEST_SUPPORT_API_KEY` and `TEST_ADD_SAMPLES` flags to ease porting The tests ported were `nbrowser` tests: `ActionLog.ts` (the first test I tend to port to anything, out of habit), `Fork.ts` (exercises a lot of doc creation paths), `HomeIntro.ts` (a lot of DocMenu exercise), and `DuplicateDocument.ts` (covers a feature known to be failing prior to this diff, the CORS tweak resolves it). Test Plan: Manually tested via `buildtools/build_core.sh`. In follow up, I want to add running the `test:docker` target in grist-core's workflows. In jenkins, only the smoke test is run. There'd be an argument for running all tests, but they include particularly slow tests, and are duplicates of tests already run (in different configuration admittedly), so I'd like to try first just using them in grist-core to gate updates to any packaged version of Grist (the docker image currently). Reviewers: alexmojaki Reviewed By: alexmojaki Subscribers: alexmojaki Differential Revision: https://phab.getgrist.com/D3176	3 years ago