RUN v3.2.4 /home/marius/Bureau/Greener/vd2e/apps/vdee ✓ __tests__/comment-template/comment-template.test.ts (2 tests) 1473ms ✓ comment template creation, editing, and deletion tests > should create, store and delete a comment-template 713ms ✓ comment template creation, editing, and deletion tests > should create a comment template and edit it 757ms ✓ __tests__/brand/brand.test.ts (3 tests) 1338ms ✓ brand creation and validation tests > should create, store, and verify a product brand 423ms ✓ brand creation and validation tests > should create a brand and edit it 458ms ✓ brand creation and validation tests > should create a brand that should be unique 454ms ✓ __tests__/product/product.test.ts (3 tests) 4253ms ✓ product creation, editing, and validation tests > should create, store, and verify a product 682ms ✓ product creation, editing, and validation tests > should create a product and edit it 2399ms ✓ product creation, editing, and validation tests > should create a product that should be unique 968ms ✓ __tests__/instance/emailPortal.test.ts (2 tests) 3687ms ✓ Integration test for email portal creation and submission > should submit portal data and verify instance updates 877ms ✓ __tests__/approach/ssc/sscApproach.test.ts (2 tests) 4567ms ✓ Integration test to edit the informations inside SSC approaches > should edit the informations of an SSC approach 1460ms ✓ Integration test to edit the informations inside SSC approaches > should edit the billing informations of an SSC approach 1098ms ✓ __tests__/approach/connector/connectorApproach.test.ts (2 tests) 5070ms ✓ Integration test to edit the informations inside connector approaches > should edit the informations of a connector approach 1884ms ✓ Integration test to edit the informations inside connector approaches > should edit the billing informations of a connector approach 1175ms ✓ __tests__/approach/isolation/isolationApproach.test.ts (2 tests) 5930ms ✓ Integration test to edit the informations inside isolation approaches > should edit the informations of an isolation approach 2423ms ✓ Integration test to edit the informations inside isolation approaches > should edit the billing informations of an isolation approach 1081ms ✓ __tests__/approach/pac/pacApproach.test.ts (2 tests) 6013ms ✓ Integration test to edit the informations inside PAC approaches > should edit the informations of a PAC approach 1554ms ✓ Integration test to edit the informations inside PAC approaches > should edit the billing informations of a PAC approach 1108ms ✓ __tests__/approach/cityHall/cityHallApproach.test.ts (2 tests) 6102ms ✓ Integration test to edit the informations inside approaches > should edit the informations of a city hall approach 1641ms ✓ Integration test to edit the informations inside approaches > should edit the billing informations of a city hall approach 1068ms ✓ __tests__/approach/consultant/consultantApproach.test.ts (2 tests) 6216ms ✓ Integration test to edit the informations inside consultant approaches > should edit the informations of a consultant approach 1809ms ✓ Integration test to edit the informations inside consultant approaches > should edit the billing informations of a consultant approach 1103ms ✓ __tests__/organism/cityHall/cityHallOrganism.test.ts (3 tests) 7566ms ✓ cityHall organism creation, editing, deleting and validation tests > should create, store, and verify a cityHall organism 739ms ✓ cityHall organism creation, editing, deleting and validation tests > should create a cityHall organism and edit it and verify the changes in the database 4859ms ✓ cityHall organism creation, editing, deleting and validation tests > should create a cityHall organism and delete it and its dependencies from the database 1728ms ✓ __tests__/organism/connector/connectorOrganism.test.ts (3 tests) 7663ms ✓ connector organism creation, editing, deleting and validation tests > should create, store, and verify a connector organism 669ms ✓ connector organism creation, editing, deleting and validation tests > should create a connetor organism and edit it and verify the changes in the database 5172ms ✓ connector organism creation, editing, deleting and validation tests > should create a connector organism and delete it and its dependencies from the database 1670ms ✓ __tests__/approach/pac/changeStatus.test.ts (4 tests) 8212ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'PENDING_RECEIPT' and save data 1556ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'PENDING_APPROVAL' and save data 1664ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'APPROVAL' and save data 1589ms ✓ Integration tests for changing the status of a PAC approach > should set the approach status to 'REFUSAL' and save data 1458ms ✓ __tests__/approach/isolation/changeStatus.test.ts (4 tests) 8584ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'PENDING_RECEIPT' and save data 1722ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'PENDING_APPROVAL' and save data 1644ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'APPROVAL' and save data 1607ms ✓ Integration tests for changing the status of an isolation approach > should set the approach status to 'REFUSAL' and save data 1484ms ✓ __tests__/approach/cityHall/changeStatus.test.ts (4 tests) 8682ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'PENDING_RECEIPT' and save data 1731ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'PENDING_APPROVAL' and save data 1626ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'APPROVAL' and save data 1958ms ✓ Integration tests for changing the status of a city hall approach > should set the approach status to 'REFUSAL' and save data 1456ms ✓ __tests__/approach/connector/changeStatus.test.ts (4 tests) 8913ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'FOLDER_READY' and save data 1078ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'PENDING_RECEIPT' and save data 2029ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'PENDING_APPOINTMENT' and save data 1327ms ✓ Integration tests for changing the status of a connector approach > should set the approach status to 'ERDF_FINALIZED' and save data 1417ms ✓ __tests__/approach/consultant/changeStatus.test.ts (6 tests) 8933ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'FILE_SENT' and save data 1178ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'FILE_PENDING' and save data 1018ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'PLANNED_VISIT' and save data 1176ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'SCHEDULED_VISIT' and save data 1257ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'TARGETED' and save data 1296ms ✓ Integration tests for changing the status of a consultant approach > should set the approach status to 'ARCHIVE' and save data 924ms ✓ __tests__/instance/changeFlowStatus.test.ts (4 tests) 9146ms ✓ Change flow status for instance elements > should change the status of datas to 'done' and verify the changes 2307ms ✓ Change flow status for instance elements > should change the status of documents to 'done' and verify the changes 1275ms ✓ Change flow status for instance elements > should change the status of task to 'done' and verify the changes 782ms ✓ Change flow status for instance elements > should confirm the enclosure feedback and verify that isCompleted is updated 633ms ✓ __tests__/lobby-resident/lobby-resident.test.ts (2 tests) 9704ms ✓ resident with lobby creation and editing > should create a resident with the associated lobby and should be stored in the database 1276ms ✓ resident with lobby creation and editing > should create a resident with the associated lobby, edit it and should be stored in the database 6495ms ✓ __tests__/approach/ssc/changeStatus.test.ts (4 tests) 9944ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'PENDING_RECEIPT' and save data 1590ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'PENDING_APPROVAL' and save data 1643ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'APPROVAL' and save data 2022ms ✓ Integration tests for changing the status of an SSC approach > should set the approach status to 'REFUSAL' and save data 1422ms ✓ __tests__/fitter/fitter.test.ts (4 tests) 18670ms ✓ fitter creation and validation tests > should create a fitter in the created state and it should be stored in the database 2094ms ✓ fitter creation and validation tests > should create a validated fitter and it should be stored in the database 1837ms ✓ fitter creation and validation tests > should create a fitter, then validate it from the edit call 9279ms ✓ fitter creation and validation tests > should delete a fitter and its dependencies from the database 5302ms ✓ __tests__/user/user.test.ts (3 tests) 15511ms ✓ user creation, editing and deleting tests > should create, store, and verify a user 3298ms ✓ user creation, editing and deleting tests > should create a user and edit it 4244ms ✓ user creation, editing and deleting tests > should create a user and delete it and its dependencies 7701ms ✓ __tests__/instance/instance.test.ts (3 tests) 21298ms ✓ Database handling of instances for city hall approaches > should create a lobby/resident with a cityHall approach and an instance for the approach 6353ms ✓ Database handling of instances for city hall approaches > should create a lobby/resident with a connector approach and an instance for the approach 6445ms ✓ Database handling of instances for city hall approaches > should create a lobby/resident with a consultant approach and an instance for the approach 6548ms Test Files 23 passed (23) Tests 70 passed (70) Start at 21:00:03 Duration 30.71s (transform 6.00s, setup 2.01s, collect 167.54s, tests 187.47s, environment 4.35s, prepare 2.36s)