92a080b704
- Add URL validation in getImageBufferFromUrl utility - Add response status validation and content-type checking - Add timeout and connection error handling with specific error messages - Validate buffer is not empty before processing - Validate file type detection results before proceeding - Ensure detected file type is actually an image format - Add proper type safety for Axios error handling This improves robustness when uploading images from URLs by: - Preventing invalid URLs from being processed - Providing clear error messages for different failure scenarios - Ensuring only valid image files are processed - Handling network errors gracefully --------- Co-authored-by: GitTensor Miner <[email protected]>
Twenty end-to-end (E2E) Testing
Prerequisite
Installing the browsers:
npx nx setup twenty-e2e-testing
Run end-to-end tests
npx nx test twenty-e2e-testing
Start the interactive UI mode
npx nx test:ui twenty-e2e-testing
Run test in specific file
npx nx test twenty-e2e-testing <filename>
Example (location of the test must be specified from the root of twenty-e2e-testing package):
npx nx test twenty-e2e-testing tests/login.spec.ts
Runs the tests in debug mode.
npx nx test:debug twenty-e2e-testing
Show report after tests
npx nx test:report twenty-e2e-testing
Q&A
Why there's path.resolve() everywhere?
That's thanks to differences in root directory when running tests using commands and using IDE. When running tests with commands,
the root directory is twenty/packages/twenty-e2e-testing, for IDE it depends on how someone sets the configuration. This way, it
ensures that no matter which IDE or OS Shell is used, the result will be the same.