I want a new built-in-parameter for access Apps of committed version with Source Control feature.
Why:
I want to run tests against the latest version for quick fixes on locally, and I want to run tests against the committed version on CI.
If the tests on the branch is running against the latest version, the test fails on main branch because the uncommitted changes are lost on main branch.
Could you elaborate on 'committed version'?
It sounds like you are looking for testing tools to test out a development branch before committing the app to the main branch that is deployed and in use, correct?
Here are some docs on running tests on Retool branches. As there are a number of different tools such playwright and Cypress as detailed in our docs here.
If there is a gap in these tools or more questions/details on how you want to use 'built-in-parameters' let me know!
Hi Jack,
Thanks for asking.
It sounds like you are looking for testing tools to test out a development branch before committing the app to the main branch that is deployed and in use, correct?
No, I've already wrote tests by Playwright for main/feature branches.
In feature branches, "https://.retool.com/tree//apps/" shows the "latest"(non-committed) App but not the "committed" App.
It means the App tested and the App merged are different.
So I want to test against the "committed" version App in CI.
Ah I understand now, thank you for elaborating and sharing the diagram!
That is odd that the URL path shows the latest "non-committed" version of the app but is not able to display the "committed" App.
I can definitely make a feature request for an extended URL param that will be able to access the branches most recent committed changes!
Thanks Jack!
I'm hoping that it will be implemented.
