founders/hackers/makers:
my main project is set up with development, staging and production environments.
all my CI (server and client) runs as github actions with each push to main and branches.
what is the benefit of setting up a testing environment?
is this overkill?
#buildinpublic
my main project is set up with development, staging and production environments.
all my CI (server and client) runs as github actions with each push to main and branches.
what is the benefit of setting up a testing environment?
is this overkill?
#buildinpublic
Comments
A testing environment allows you to automatically let unit and integration tests run. They make sure your code does what it's supposed to do. Having said that, it's a ton of work.
So I'd rather validate the business model first or only have very basic tests.
You do a lot of stuff manually behind the scenes, pushing releases, payments etc and to the outside world it may look automated, but its not.
Because else it's this trap you can observe so often: things get automated without even asking if it's necessary (yet).
Having said that, at the same time it's important to build an infrastructure that is maintainable. Such a nuanced balance depending on the case.
Similar to the 'you must never duplicate anything' rule, which sometimes makes things less maintainable/understandable.