Integration test suite first steps... #347
No reviewers
Labels
No Label
bug
build
ci/cd
contributing
critical
design
documentation
duplicate
enhancement
help wanted
invalid
meta
question
release
release-candidate
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/abra#347
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "integration-tests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As planned with @3wordchant, optimise for local developer workflow first and patch
abra
to support a~/.abra_test
directory. This can be configured withABRA_TEST=...
. Maybe you had a thought on the naming of this var @3wordchant? This is working well so far and I even caught a bug already, which makes me feel like it's the way to go. With a dedicated test server setup later on, I think we could get a solid test coverage forabra
with this. Lemme know what you think folks! Kept the diff small so it's easy to review / grok before moving ahead.@ -0,0 +10,4 @@
_build_kadabra() {
if [[ ! -e "$ROOT/kadabra" ]]; then
cd "$ROOT" && make build-dev
Oops, that's wrong, Need a dedicated
kadabra
makefile target. TODO 🤓@ -17,1 +17,3 @@
var ABRA_DIR = os.ExpandEnv("$HOME/.abra")
// getBaseDir retrieves the Abra base directory.
func getBaseDir() string {
home := os.ExpandEnv("$HOME/.abra")
What about making the env var
ABRA_DIR
, and defaulting to$HOME/.abra
? then for testsABRA_DIR=$HOME/.abra_test
, and folks could also choose to put the directory elsewhere for homedir-neatness reasons, or in the case of an immutable home dir.