RUN v3.2.4 /home/marius/Bureau/Greener/vd2e/apps/vdee ✓ __tests__/brand/brand.test.ts (3 tests) 1416ms ✓ brand creation and validation tests > should create, store, and verify a product brand 548ms ✓ brand creation and validation tests > should create a brand and edit it 407ms ✓ brand creation and validation tests > should create a brand that should be unique 460ms ✓ __tests__/comment-template/comment-template.test.ts (2 tests) 1578ms ✓ comment template creation, editing, and deletion tests > should create, store and delete a comment-template 892ms ✓ comment template creation, editing, and deletion tests > should create a comment template and edit it 683ms ✓ __tests__/product/product.test.ts (3 tests) 4063ms ✓ product creation, editing, and validation tests > should create, store, and verify a product 653ms ✓ product creation, editing, and validation tests > should create a product and edit it 2195ms ✓ product creation, editing, and validation tests > should create a product that should be unique 957ms ✓ __tests__/instance/emailPortal.test.ts (2 tests) 3013ms ✓ Integration test for email portal creation and submission > should submit portal data and verify instance updates 709ms ✓ __tests__/approach/consultant/consultantApproach.test.ts (2 tests) 4611ms ✓ Integration test to edit the informations inside consultant approaches > should edit the informations of a consultant approach 1530ms ✓ Integration test to edit the informations inside consultant approaches > should edit the billing informations of a consultant approach 1134ms ✓ __tests__/approach/pac/pacApproach.test.ts (2 tests) 4495ms ✓ Integration test to edit the informations inside PAC approaches > should edit the informations of a PAC approach 1435ms ✓ Integration test to edit the informations inside PAC approaches > should edit the billing informations of a PAC approach 1150ms ✓ __tests__/approach/ssc/sscApproach.test.ts (2 tests) 4613ms ✓ Integration test to edit the informations inside SSC approaches > should edit the informations of an SSC approach 1475ms ✓ Integration test to edit the informations inside SSC approaches > should edit the billing informations of an SSC approach 1158ms ✓ __tests__/approach/cityHall/cityHallApproach.test.ts (2 tests) 4760ms ✓ Integration test to edit the informations inside approaches > should edit the informations of a city hall approach 1571ms ✓ Integration test to edit the informations inside approaches > should edit the billing informations of a city hall approach 1151ms ✓ __tests__/approach/connector/connectorApproach.test.ts (2 tests) 5077ms ✓ Integration test to edit the informations inside connector approaches > should edit the informations of a connector approach 2175ms ✓ Integration test to edit the informations inside connector approaches > should edit the billing informations of a connector approach 1141ms ✓ __tests__/approach/isolation/isolationApproach.test.ts (2 tests) 5816ms ✓ Integration test to edit the informations inside isolation approaches > should edit the informations of an isolation approach 2641ms ✓ Integration test to edit the informations inside isolation approaches > should edit the billing informations of an isolation approach 1197ms ✓ __tests__/organism/connector/connectorOrganism.test.ts (3 tests) 7411ms ✓ connector organism creation, editing, deleting and validation tests > should create, store, and verify a connector organism 1108ms ✓ connector organism creation, editing, deleting and validation tests > should create a connetor organism and edit it and verify the changes in the database 4363ms ✓ connector organism creation, editing, deleting and validation tests > should create a connector organism and delete it and its dependencies from the database 1678ms ✓ __tests__/approach/connector/changeStatus.test.ts (4 tests) 7118ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'FOLDER_READY' and save data 921ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'PENDING_RECEIPT' and save data 1956ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'PENDING_APPOINTMENT' and save data 1191ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'ERDF_FINALIZED' and save data 1387ms ✓ __tests__/approach/pac/changeStatus.test.ts (4 tests) 7783ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'PENDING_RECEIPT' and save data 1343ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'PENDING_APPROVAL' and save data 1456ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'APPROVAL' and save data 1506ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'REFUSAL' and save data 1727ms ✓ __tests__/approach/ssc/changeStatus.test.ts (4 tests) 7929ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'PENDING_RECEIPT' and save data 1330ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'PENDING_APPROVAL' and save data 1462ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'APPROVAL' and save data 1729ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'REFUSAL' and save data 1713ms ✓ __tests__/approach/cityHall/changeStatus.test.ts (4 tests) 8183ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'PENDING_RECEIPT' and save data 1481ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'PENDING_APPROVAL' and save data 1419ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'APPROVAL' and save data 1485ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'REFUSAL' and save data 2000ms ✓ __tests__/approach/isolation/changeStatus.test.ts (4 tests) 8609ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'PENDING_RECEIPT' and save data 1544ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'PENDING_APPROVAL' and save data 1475ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'APPROVAL' and save data 1469ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'REFUSAL' and save data 2136ms ✓ __tests__/instance/changeFlowStatus.test.ts (4 tests) 8931ms ✓ Change flow status for instance elements > should change the status of datas to 'done' and verify the changes 2427ms ✓ Change flow status for instance elements > should change the status of documents to 'done' and verify the changes 1247ms ✓ Change flow status for instance elements > should change the status of task to 'done' and verify the changes 1275ms ✓ Change flow status for instance elements > should confirm the enclosure feedback and verify that isCompleted is updated 1339ms ✓ __tests__/lobby-resident/lobby-resident.test.ts (2 tests) 9904ms ✓ resident with lobby creation and editing > should create a resident with the associated lobby and should be stored in the database 1389ms ✓ resident with lobby creation and editing > should create a resident with the associated lobby, edit it and should be stored in the database 7930ms ✓ __tests__/approach/consultant/changeStatus.test.ts (6 tests) 10302ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'FILE_SENT' and save data 1196ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'FILE_PENDING' and save data 947ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'PLANNED_VISIT' and save data 1141ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'SCHEDULED_VISIT' and save data 1188ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'TARGETED' and save data 1803ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'ARCHIVE' and save data 2050ms ✓ __tests__/organism/cityHall/cityHallOrganism.test.ts (3 tests) 11039ms ✓ cityHall organism creation, editing, deleting and validation tests > should create, store, and verify a cityHall organism 1710ms ✓ cityHall organism creation, editing, deleting and validation tests > should create a cityHall organism and edit it and verify the changes in the database 5483ms ✓ cityHall organism creation, editing, deleting and validation tests > should create a cityHall organism and delete it and its dependencies from the database 3306ms ✓ __tests__/user/user.test.ts (3 tests) 19335ms ✓ user creation, editing and deleting tests > should create, store, and verify a user 1100ms ✓ user creation, editing and deleting tests > should create a user and edit it 3740ms ✓ user creation, editing and deleting tests > should create a user and delete it and its dependencies 14246ms ✓ __tests__/instance/instance.test.ts (3 tests) 21083ms ✓ Database handling of instances for city hall approaches > should create a lobby/resident with a cityHall approach and an instance for the approach 6392ms ✓ Database handling of instances for city hall approaches > should create a lobby/resident with a connector approach and an instance for the approach 8015ms ✓ Database handling of instances for city hall approaches > should create a lobby/resident with a consultant approach and an instance for the approach 6165ms ✓ __tests__/fitter/fitter.test.ts (4 tests) 28429ms ✓ fitter creation and validation tests > should create a fitter in the created state and it should be stored in the database 2027ms ✓ fitter creation and validation tests > should create a validated fitter and it should be stored in the database 1901ms ✓ fitter creation and validation tests > should create a fitter, then validate it from the edit call 7898ms ✓ fitter creation and validation tests > should delete a fitter and its dependencies from the database 16336ms Test Files 23 passed (23) Tests 70 passed (70) Start at 20:48:38 Duration 31.62s (transform 6.01s, setup 2.15s, collect 169.75s, tests 195.50s, environment 4.61s, prepare 2.40s)