refactor(test): rename test-everything → test-full

Shorter, clearer name for the target that runs every test in the repo
(all suites + integration + integration2 + upgrade + fuzz).

Author: mlwelles

AGENTS.md

@@ -1,16 +1,42 @@
 # Repository Guidelines
 
 ## Project Structure & Module Organization
-The Go module is rooted here, with entrypoints and CLI tooling under `dgraph/` for Alpha, Zero, Live, and companions. Core execution sits in `worker/`, `query/`, and `posting/`, the GraphQL adapters in `graphql/`, and shared helpers in packages like `x/` and `testutil/`. Protocol definitions live in `protos/` (regenerate via `make regenerate` inside that folder). Integration harnesses are in `t/`, broader system scenarios in `systest/`, and container assets under `contrib/` and `compose/`.
+
+The Go module is rooted here, with entrypoints and CLI tooling under `dgraph/` for Alpha, Zero,
+Live, and companions. Core execution sits in `worker/`, `query/`, and `posting/`, the GraphQL
+adapters in `graphql/`, and shared helpers in packages like `x/` and `testutil/`. Protocol
+definitions live in `protos/` (regenerate via `make regenerate` inside that folder). Integration
+harnesses are in `t/`, broader system scenarios in `systest/`, and container assets under `contrib/`
+and `compose/`.
 
 ## Build, Test, and Development Commands
-Use `make dgraph` to compile the Linux AMD64 binaries into `./dgraph/dgraph`, or `make install` to drop them into `$GOPATH/bin`. Run `go test ./path/to/package` for focused checks or `go test ./...` for a fast repo-wide sweep. `make test` (no args) runs the default suite (`unit,systest,core` + `integration2`, ~30 min); use `make test SUITE=all` for all t/ runner suites or `make test-everything` for every test in the repo. Keep Docker running for integration tests. When debugging version info, `make version` surfaces the embedded build metadata.
+
+Use `make dgraph` to compile the Linux AMD64 binaries into `./dgraph/dgraph`, or `make install` to
+drop them into `$GOPATH/bin`. Run `go test ./path/to/package` for focused checks or `go test ./...`
+for a fast repo-wide sweep. `make test` (no args) runs the default suite (`unit,systest,core` +
+`integration2`, ~30 min); use `make test SUITE=all` for all t/ runner suites or `make test-full` for
+every test in the repo. Keep Docker running for integration tests. When debugging version info,
+`make version` surfaces the embedded build metadata.
 
 ## Coding Style & Naming Conventions
-Follow standard Go conventions: exported identifiers start with capitals, packages use lowercase, and tests use `TestXxx` names. Format every change with `go fmt` (or `gofmt -w`) before committing; CI runs `golangci-lint`, so keep `//nolint` waivers rare and justified. Maintain the SPDX license header block on all new source files and avoid introducing unused helpers or dead code.
+
+Follow standard Go conventions: exported identifiers start with capitals, packages use lowercase,
+and tests use `TestXxx` names. Format every change with `go fmt` (or `gofmt -w`) before committing;
+CI runs `golangci-lint`, so keep `//nolint` waivers rare and justified. Maintain the SPDX license
+header block on all new source files and avoid introducing unused helpers or dead code.
 
 ## Testing Guidelines
-Unit tests live beside their packages in `_test.go` files and run with `go test`. The `t/` harness drives integration clusters; add new scenarios under targeted subdirectories. `systest/` and `graphql/e2e/` capture longer system flows—mirror their layout when extending coverage. Before opening a PR, run `go test ./...` and the `t` or `systest` suites touched by your change, and include regression tests for new behaviour.
+
+Unit tests live beside their packages in `_test.go` files and run with `go test`. The `t/` harness
+drives integration clusters; add new scenarios under targeted subdirectories. `systest/` and
+`graphql/e2e/` capture longer system flows—mirror their layout when extending coverage. Before
+opening a PR, run `go test ./...` and the `t` or `systest` suites touched by your change, and
+include regression tests for new behaviour.
 
 ## Commit & Pull Request Guidelines
-Recent history favors `type(scope): short message` commits (for example, `fix(compose): ...` or `chore: ...`). Keep commits atomic with clear intent, sign when possible, and reference issues using `Fixes #1234` when applicable. PRs should describe the motivation, summarize testing (`go test ./...`, `make test`, etc.), and call out configuration or data migrations. Include doc updates for user-facing behaviour changes and attach CLI output or screenshots if tooling UX shifts.
+
+Recent history favors `type(scope): short message` commits (for example, `fix(compose): ...` or
+`chore: ...`). Keep commits atomic with clear intent, sign when possible, and reference issues using
+`Fixes #1234` when applicable. PRs should describe the motivation, summarize testing
+(`go test ./...`, `make test`, etc.), and call out configuration or data migrations. Include doc
+updates for user-facing behaviour changes and attach CLI output or screenshots if tooling UX shifts.

CONTRIBUTING.md

@@ -148,7 +148,7 @@ The simplest way to run tests is via Make:
 make test
 
 # Run every test in the repo
-make test-everything
+make test-full
 
 # Run specific test types
 make test-unit          # Unit tests only (no Docker)

Makefile

@@ -165,8 +165,8 @@ test-load: ## Heavy load tests (i.e. 'make test SUITE=load')
 	$(if $(filter command line,$(origin SUITE)),$(error SUITE= cannot be passed to test-load; use 'make test SUITE=...' instead))
 	@SUITE=load $(MAKE) test
 
-.PHONY: test-everything
-test-everything: ## Every test: all suites + integration + integration2 + upgrade + fuzz
+.PHONY: test-full
+test-full: ## Every test: all suites + integration + integration2 + upgrade + fuzz
 	$(MAKE) test-suites
 	$(MAKE) test-integration
 	$(MAKE) test-integration2

TESTING.md

@@ -308,7 +308,7 @@ The simplest way to run tests:
 make test
 
 # Run every test in the repo (all suites + all tag-based tests + fuzz)
-make test-everything
+make test-full
 
 # Common shortcuts (run 'make help' for full list)
 make test-suites        # All t/ runner suites (i.e. 'make test SUITE=all')
@@ -342,8 +342,8 @@ For more control, pass variables to `make test`:
 | `FUZZ`     | Enable fuzz testing                | `make test FUZZ=1`              |
 | `FUZZTIME` | Fuzz duration per package          | `make test FUZZ=1 FUZZTIME=60s` |
 
-**Precedence:** `TAGS` > `FUZZ` > `SUITE` > default (first match wins). When no
-variable is set, `make test` runs suites `unit,systest,core` plus `integration2`.
+**Precedence:** `TAGS` > `FUZZ` > `SUITE` > default (first match wins). When no variable is set,
+`make test` runs suites `unit,systest,core` plus `integration2`.
 
 ### Examples
 
@@ -1293,7 +1293,7 @@ The following items from the original wishlist have been implemented:
 - **✅ Unified test interface:** A single `make test` entry point that accepts arguments to run any
   test type (unit, integration, integration2, upgrade, fuzz) with environment variables for control.
   The default (`make test` with no args) runs `unit,systest,core` suites plus `integration2` for a
-  fast feedback loop (~30 min). Use `make test-everything` to run all tests.
+  fast feedback loop (~30 min). Use `make test-full` to run all tests.
 
 - **✅ Example commands that "just work":** The following now work as expected: