Open petecooper opened 3 years ago
Nice, thank you. This is interesting as it's multifaceted:
The above might well contain incompatible goals and the automated test environment needs to be separate from the manual one. Not sure yet. Would be nice to run it all from one place but unsure of the mechanics and general level of script-fu required to get it singing.
Revisiting this since it got a bit lost…
Anything to add to https://github.com/textpattern/unit-test/issues/2#issuecomment-801233422 @Bloke, or is that a good jumping off point?
I think the post above encapsulates most of what would be desirable in such an instance.
Not sure how much is doable. But if it's not easily scriptable then I think it damn well should be, so it's an opportunity to tweak core to allow such an environment to be spun up more easily.
Q1: is it possible to plonk a cookie file in an instance and have it log in? Or could we maybe manually log in once, grab the cookie and stick it in this repo. If that's possible, the downside is it expires after 30 days so we would need to find a way to refresh the file periodically. Or hack it so the expiry is never.
Is there scope for a unit-test
branch that doesn't need a login and is essentially dev
with patched code? That way we bypass the cookie and it won't need maintaining (also allows others to have a 'turbo debug' version for their own hacking.
Absolutely. The auto login would only be for automatic unit testing that could report if anything broke when the code base was automatically rebuilt with the latest bleeding edge code. If it's only for manual unit testing then yeah, patched code base with all the unit tests we can design would be awesome.
NTS