4 ms·
The times I've seen more complex testing set-ups that use actions is normally some combination of: 1. Testing involves some kind of complex environment 2. IT in
by benrutter 3y ago
The times I've seen more complex testing set-ups that use actions is normally some combination of:
1. Testing involves some kind of complex environment
2. IT infrastructure in some corporations makes setting up that environment impossible.
I worked once in a role where I had to write a library aimed for working with spark, but getting spark (i.e. java etc) installed on my machine involved weeks worth of requests and escalations to IT.
A lot of libraries (I'm thinking of adlfs as a good example which interacts with azure data lake file systrmd) have to have relatively complex testing involving docker by nature of what they are.
None if those points make "put in a PR to run tests" a good or justifiable workflow. But I understand how people wind up falling into that trap.