Files
twenty/packages/twenty-server/test/integration/metadata/utils/warn-if-no-error-but-expected-to-fail.util.ts
T
Paul Rastoin 59d90bedaa Integration testing v2 enum field types fail and success path (#14010)
# Introduction
Migrating and improving performances of field enum integrations tests
success and failing tests cases to be using the new v2 api

## Discovered issue
When deleting an object in v1 it will leave related enums until the
object is re-created
Something not done anymore within the create in v2 but in the delete
operation
We should implem an upgrade command to remove such relicas

## Bugs
- Update/create default value multi select runner wrong sql query -> FIX
- Update default value multi select regression, we should allow option
without an id to be inserted -> FIX
- default value compare dynamic json stringify convertion or not in
compare tools for object and fields
2025-08-28 10:23:04 +00:00

18 lines
491 B
TypeScript

import { isDefined } from 'class-validator';
import { type Response } from 'supertest';
type WarnIfNoErrorButExpectedToFailInput = {
response: Response;
errorMessage: string;
};
export const warnIfNoErrorButExpectedToFail = ({
response,
errorMessage,
}: WarnIfNoErrorButExpectedToFailInput) => {
if (!isDefined(response.body.errors) || response.body.errors.length === 0) {
expect(false).toEqual(errorMessage);
}
expect(response.body.errors.length).toBeGreaterThan(0);
};