Jérémy M eef7f1661d feat: add integration tests (#6923) ... ### Summary This PR introduces several integration tests, a mix of manually written tests and those generated using the `generate-integration-tests` Python script located in the `scripts` folder. ### Tests Added: - **Authentication tests**: Validating login, registration, and token handling. - **FindMany queries**: Fetching multiple records for all existing entities that do not require input arguments. ### How the Integration Tests Work: - A `setupTest` function is called during the Jest test run. This function initializes a test instance of the application and exposes it on a dedicated port. - Since tests are executed in isolated workers, they do not have direct access to the in-memory app instance. Instead, the tests query the application through the exposed port. - A static accessToken is used, this one as a big expiration time so it will never expire (365 years) - The queries are executed, and the results are validated against expected outcomes. ### Current State and Next Steps: - These tests currently run using the existing development seed data. We plan to introduce more comprehensive test data using `faker` to improve coverage. - At the moment, the only mutation tests implemented are for authentication. Future updates should include broader mutation testing for other entities. --------- Co-authored-by: Charles Bochet <charles@twenty.com>		2024-09-20 11:02:52 +02:00
..
common.d.ts	Compile with swc on twenty-server (#4863)	2024-04-14 09:09:51 +02:00
express.d.ts	Trigger workflow run manually (#6696)	2024-08-21 17:41:26 +02:00
jest.d.ts	feat: add integration tests (#6923)	2024-09-20 11:02:52 +02:00