GiselleSerate
commented
5 years ago I believe in the power of CircleCI and containers.
Open GiselleSerate opened 6 years ago
GiselleSerate
commented
5 years ago I believe in the power of CircleCI and containers.
aryarm
commented
5 years ago On the issue of including the test suite with the repo: I think the standard solution is to use GitHub releases. Most of the super official software I've seen will use that instead of having their users git clone the repo
aryarm
commented
4 years ago This issue is possibly a duplicate of #36 At least, resolving this issue will probably resolve that one, as well
cause it would be nice to have one of those It would also make supporting new systems really easy to determine. Here's the list of supported systems for bats.
Here's a possibly useful rundown of various test frameworks we could use. I like the sound of
bats(but don't use the link in the medium article cause this is the maintained version, I accidentally installed the old version and I'm trying to get it off goodbye). Maybe influenced by the fact that the author and one of the commentors used and liked it, but that's what articles are for, no? (Also I like the way he uses that install script . . . maybe we could take a few tips from the way it works, cause you install this almost exactly the way that you'd want to installmyaliases.Also to be considered, should we be pushing the code with the testing framework? I want to have it easily clonable from anywhere with the testing framework but I don't think our end users need the testing framework. This is another thing I wanted to read up on, because I'm sure someone's written up a good workflow for this. Until I figure out the preferred workflow, I'm going to make a branch off master to try to make whichever test framework functional. According to some StackOverflow posts, we should be pushing the tests. Maybe in a separate folder. I saw the phrase "living documentation" which I think is pretty poetic and hopefully our tests will be like that? Anyway I guess I'll write up tests for a very basic function just to make sure the test framework is happy and functional and then we can write in tests for the rest of the repo. They shouldn't be too bulky. At some point maybe we can try wrangling branches such that tests don't go out with production code, but I'll keep the tests off master (@GiselleSerate yes we're keeping the tests off master) until we can figure out a way to get code to end users without also giving them all our tests. I also don't quite trust my git expertise (and it seems like bad practice anyway) to merge this into master and then later on pull the tests out of master.