10 Commits

Author	SHA1	Message	Date
Abdullah Atta	32b8b008f2	web: make export tests pass	2023-08-01 20:39:16 +05:00
Abdullah Atta	bbb43bc8b4	web: replace date-time in test snapshot with xxx	2023-06-05 15:29:10 +05:00
Abdullah Atta	060952697a	web: bring back title in context menu	2023-02-13 18:13:54 +05:00
Abdullah Atta	a0579278c9	web: fix all e2e tests	2023-02-13 18:13:54 +05:00
Abdullah Atta	9116a24392	global: update license year to 2023	2023-01-16 13:48:28 +05:00
Abdullah Atta	89123c0be5	web: right click on selected items deselects them	2022-09-29 15:55:52 +05:00
Ammar Ahmed	e5e965415d	feat: realtime & auto sync for all users (#944)	2022-09-20 18:33:55 +05:00
Abdullah Atta	02a0ccebee	web: fix failing tests	2022-09-18 16:37:33 +05:00
Abdullah Atta	7cc8b74a7a	web: add more waitFors for failing tests	2022-09-17 00:45:29 +05:00
Abdullah Atta	d31a43b463	web: rewrite the whole test suite to be more resilient ... **Why?** The old test suite was a confusing mess, hard to maintain, update, and add more tests to. It lacked a much needed layer of expressivity & the reusable functions were all over the place. Since it used a global `page` (by mistake), it couldn't run in parallel. Moreover, the global `page` approach caused random flakiness. All the above reasons led to this OM (Object Model) based approach to tests. The tests are now much more expressive, reslient, resuable & easier to maintain. During the rewriting process I also added a couple more tests (about 10) so this is a net improvement. Previously, running the tests were also quite slow (15-25s avg). This has now been improved to (5-8s avg) by running the tests in production. This means the app now requires to be built before running the tests: ```sh npm run build:test:web # this is only required once npm run test:web ```	2022-09-14 11:50:24 +05:00