expect_tests/test/data/README - Issue 709853003: New expect_tests UI

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: expect_tests/test/data/README

Issue 709853003: New expect_tests UI (Closed) Base URL: https://chromium.googlesource.com/infra/testing/expect_tests@shebang

Patch Set: Fixed nits Created 6 years, 1 month ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1 This directory (test/data) contains fake test suites used for the

	2 expect_tests test suite. They are used by the tests present in test/, and by

	3 themselves do not test anything (e.g. there are self.assertTrue(True) in

	4 many places)

	5

	6 Thus, the structure here is highly connected with the tests present in test/.

	7 Adding or removing a test method in test/data is likely to break a test in

	8 test/.

	9

	10 Example: test/pipeline.py:TestListingTest.test_get_test_gens_package lists the

	11 tests present in test/data/package1, with various options. The expected output

	12 is written in test/pipeline_test.py itself, and should match the actual

	13 structure in test/data.

	14

	15 Additional information can be found in other READMEs.

OLD	NEW