facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-10 08:47:12 +03:00
Code Issues Projects Releases Wiki Activity
e308419b58
sapling/eden/scm/tests/test-autofix.t

30 lines
619 B
Perl
Raw Normal View History

tests: enable chg for 572 tests Summary: Add `#chg-compatible` to 572 tests that seem to pass with chg enabled. This should make them run faster. Reviewed By: xavierd Differential Revision: D18870507 fbshipit-source-id: fe895e733efffc9286cd3d17c7a156c803124395
2019-12-10 02:24:31 +03:00
#chg-compatible
testutil: add "eq" assertion with autofix ability Summary: The "eq" API is similar to `assert_eq!` in Rust, with the autofix ability. Reviewed By: xavierd Differential Revision: D16168821 fbshipit-source-id: bf7dcfd24c42dee30c54aeeaa71eccab78a8f0f6
2019-07-18 06:59:57 +03:00
#require parso
$ cat > a.py << EOF
> from testutil.autofix import eq
testutil/dott: implement autofix for commands without outputs Summary: Comparing to `.t` tests, `dott` Python tests cannot autofix commands without outputs. This diff makes it able to do so. It's less strict than the AST parsing (for example, it does not handle `#` comments precisely). But practically it might be good enough. We can update it to use real AST parsing if it becomes an issue. This should make `dott` Python tests easier to use. Reviewed By: xavierd Differential Revision: D17277285 fbshipit-source-id: 11ef6ec4327a6547d49b544c63bc000a3c351947
2019-09-10 22:58:22 +03:00
> from testutil.dott import sh
testutil: add "eq" assertion with autofix ability Summary: The "eq" API is similar to `assert_eq!` in Rust, with the autofix ability. Reviewed By: xavierd Differential Revision: D16168821 fbshipit-source-id: bf7dcfd24c42dee30c54aeeaa71eccab78a8f0f6
2019-07-18 06:59:57 +03:00
> eq(1 + 2, 0)
> eq(list(range(3)), None)
> eq("\n".join(map(str,range(3))), None)
testutil/dott: implement autofix for commands without outputs Summary: Comparing to `.t` tests, `dott` Python tests cannot autofix commands without outputs. This diff makes it able to do so. It's less strict than the AST parsing (for example, it does not handle `#` comments precisely). But practically it might be good enough. We can update it to use real AST parsing if it becomes an issue. This should make `dott` Python tests easier to use. Reviewed By: xavierd Differential Revision: D17277285 fbshipit-source-id: 11ef6ec4327a6547d49b544c63bc000a3c351947
2019-09-10 22:58:22 +03:00
> sh % "printf foo"
> sh % "printf bar" == "baz"
testutil: add "eq" assertion with autofix ability Summary: The "eq" API is similar to `assert_eq!` in Rust, with the autofix ability. Reviewed By: xavierd Differential Revision: D16168821 fbshipit-source-id: bf7dcfd24c42dee30c54aeeaa71eccab78a8f0f6
2019-07-18 06:59:57 +03:00
> EOF
tests: change some 'python' to 'hg debugpython' Summary: In the future `python` will no longer be able to import `bindings`. Change them to `hg debugpython` so they stay compatible. I dropped the "custom hghave" feature. It breaks and I don't think there are users of it. Reviewed By: singhsrb Differential Revision: D17429689 fbshipit-source-id: 96e55ef25a027bd4ad33fc279f27c1d5cbed6861
2019-09-21 03:43:59 +03:00
$ hg debugpython -- a.py 2>&1 | tail -1
testutil/dott: simplify error messages Summary: The current error message is a bit noisy. Let's just get to the point about the filename and line number that is interesting without tracebacks. This only affects functions using the `autofix.eq` API, other kinds of exceptions will have tracebacks as usual. Before, run-tests.py (19 lines): --- test-empty-t.py.out +++ test-empty-t.py.err @@ -0,0 +1,14 @@ +Traceback (most recent call last): + File "hg/tests/test-empty-t.py", line 71, in <module> + """ + File "hg/tests/testutil/dott/shobj.py", line 89, in __eq__ + autofix.eq(out, rhs, nested=1, eqfunc=eqglob) + File "hg/tests/testutil/autofix.py", line 93, in eq + raise AssertionError("actual != expected\n%s" % diff) +AssertionError: actual != expected +--- expected ++++ actual +@@ -1 +1 @@ +-someheads ++allheads + ERROR: test-empty-t.py output changed Before, run directly via python (13 lines): Traceback (most recent call last): File "test-empty-t.py", line 71, in <module> """ File "hg/tests/testutil/dott/shobj.py", line 89, in __eq__ autofix.eq(out, rhs, nested=1, eqfunc=eqglob) File "hg/tests/testutil/autofix.py", line 93, in eq raise AssertionError("actual != expected\n%s" % diff) AssertionError: actual != expected --- expected +++ actual @@ -1 +1 @@ -someheads +allheads After, run-tests.py (8 lines): --- test-empty-t.py:71 (expected) +++ test-empty-t.py:71 (actual) @@ -1 +1 @@ -someheads +allheads ERROR: test-empty-t.py output changed After, run directly (5 lines): % python test-empty-t.py --- test-empty-t.py:71 (expected) +++ test-empty-t.py:71 (actual) @@ -1 +1 @@ -someheads +allheads Reviewed By: xavierd Differential Revision: D17277286 fbshipit-source-id: a48d4d1e817f67e221a901977e0c0f8bdc1a62ab
2019-09-10 22:58:22 +03:00
a.py:3: 3 != 0
testutil: add "eq" assertion with autofix ability Summary: The "eq" API is similar to `assert_eq!` in Rust, with the autofix ability. Reviewed By: xavierd Differential Revision: D16168821 fbshipit-source-id: bf7dcfd24c42dee30c54aeeaa71eccab78a8f0f6
2019-07-18 06:59:57 +03:00
tests: change some 'python' to 'hg debugpython' Summary: In the future `python` will no longer be able to import `bindings`. Change them to `hg debugpython` so they stay compatible. I dropped the "custom hghave" feature. It breaks and I don't think there are users of it. Reviewed By: singhsrb Differential Revision: D17429689 fbshipit-source-id: 96e55ef25a027bd4ad33fc279f27c1d5cbed6861
2019-09-21 03:43:59 +03:00
$ hg debugpython -- a.py --fix
testutil: add "eq" assertion with autofix ability Summary: The "eq" API is similar to `assert_eq!` in Rust, with the autofix ability. Reviewed By: xavierd Differential Revision: D16168821 fbshipit-source-id: bf7dcfd24c42dee30c54aeeaa71eccab78a8f0f6
2019-07-18 06:59:57 +03:00
$ cat a.py
from testutil.autofix import eq
testutil/dott: implement autofix for commands without outputs Summary: Comparing to `.t` tests, `dott` Python tests cannot autofix commands without outputs. This diff makes it able to do so. It's less strict than the AST parsing (for example, it does not handle `#` comments precisely). But practically it might be good enough. We can update it to use real AST parsing if it becomes an issue. This should make `dott` Python tests easier to use. Reviewed By: xavierd Differential Revision: D17277285 fbshipit-source-id: 11ef6ec4327a6547d49b544c63bc000a3c351947
2019-09-10 22:58:22 +03:00
from testutil.dott import sh
testutil: add "eq" assertion with autofix ability Summary: The "eq" API is similar to `assert_eq!` in Rust, with the autofix ability. Reviewed By: xavierd Differential Revision: D16168821 fbshipit-source-id: bf7dcfd24c42dee30c54aeeaa71eccab78a8f0f6
2019-07-18 06:59:57 +03:00
eq(1 + 2, 3)
eq(list(range(3)), [0, 1, 2])
eq("\n".join(map(str,range(3))), r"""
0
1
2""")
testutil/dott: implement autofix for commands without outputs Summary: Comparing to `.t` tests, `dott` Python tests cannot autofix commands without outputs. This diff makes it able to do so. It's less strict than the AST parsing (for example, it does not handle `#` comments precisely). But practically it might be good enough. We can update it to use real AST parsing if it becomes an issue. This should make `dott` Python tests easier to use. Reviewed By: xavierd Differential Revision: D17277285 fbshipit-source-id: 11ef6ec4327a6547d49b544c63bc000a3c351947
2019-09-10 22:58:22 +03:00
sh % "printf foo" == 'foo'
sh % "printf bar" == 'bar'
Reference in New Issue Copy Permalink