Failures in these specs show up like this today:   Which are practically impossible to troubleshoot, assert the order of keys in objects which we don't really want/need, and is failing on Postgres. Instead, in this PR, we use `.deep.eq` to assert them, which is almost the same thing in practice, but doesn't assert the key order in serialization.  /test fork <!-- This is an auto-generated comment: Cypress test results --> > [!WARNING] > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/9691146519> > Commit: d3da957b5362e0314e11c7589e43fb526e4317d6 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9691146519&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Fork` > It seems like **no tests ran** 😔. We are not able to recognize it, please check <a href="https://github.com/appsmithorg/appsmith/actions/runs/9691146519" target="_blank">workflow here</a>. <!-- end of auto-generated comment: Cypress test results --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Tests** - Refactored test cases to improve the scope management and comparison logic within the test blocks. This change enhances the reliability and maintainability of the test suite. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| Apps | ||
| ClientSide | ||
| Enterprise/AdminSettings | ||
| ServerSide | ||