Martin von Zweigbergk 0f7054e8c3 tests: wherever we test with only one backend, use the test backend ... I don't think there's any reason to use the local backend in tests instead of using the stricter test backend. I think we should generally use the test backend in tests and only use the local backend or git backend when there's a particular reason to do so (such as in `test_bad_locking` where the on-disk directory structure matters). But this patch only deals with the simpler cases where we were only testing with the local backend.		2023-09-19 20:49:41 -07:00
..
benches	cargo: rename crates from jujutsu/jujutsu-lib to jj-cli/jj-lib	2023-07-09 06:40:43 +02:00
gen-protos	Use { workspace = true } to appease VS Code's Cargo.toml parser	2023-08-22 21:38:53 -07:00
src	backend: move constant functions first	2023-09-19 05:24:51 -07:00
tests	tests: wherever we test with only one backend, use the test backend	2023-09-19 20:49:41 -07:00
testutils	tests: wherever we test with only one backend, use the test backend	2023-09-19 20:49:41 -07:00
Cargo.toml	merged_tree: add diff iterator	2023-08-25 06:40:36 -07:00