docs/testing/writing_layout_tests.md - Issue 2617083002: Remove <title> in writing_layout_tests documentation

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

Unified Diff: docs/testing/writing_layout_tests.md

Issue 2617083002: Remove <title> in writing_layout_tests documentation (Closed)

Patch Set: Remove mentioning of <title> in writing_layout_tests.md since it doesnt appear in test results and … Created 3 years, 11 months ago

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

Jump to:

Index: docs/testing/writing_layout_tests.md

diff --git a/docs/testing/writing_layout_tests.md b/docs/testing/writing_layout_tests.md

index f2767c206dedb34307ae5b5972ed16a7271b5d22..13d563b53090a7a511cf39539eab438c33eac2dd 100644

--- a/docs/testing/writing_layout_tests.md

+++ b/docs/testing/writing_layout_tests.md

@@ -338,7 +338,6 @@ in order to follow the minimality guideline, the test omits the tags `<html>`,

```html

<!doctype html>

-<title>JavaScript: the true literal</title>

@@ -375,9 +374,7 @@ promise_test(() => {

Some points that are not immediately obvious from the example:

-* The `<meta name="assert">` describes the purpose of the entire file, and

- is not redundant to `<title>`. Don't add a `<meta name="assert">` when the

- information in the `<title>` is sufficient.

+* The `<meta name="assert">` describes the purpose of the entire file.

* When calling an `assert_` function that compares two values, the first

argument is the actual value (produced by the functionality being tested), and

the second argument is the expected value (known good, golden). The order

@@ -393,9 +390,6 @@ Some points that are not immediately obvious from the example:

redundant.

* Do not start test case descriptions with redundant terms like "Testing"

or "Test for".

- * Test files with a single test case should omit the test case description.

- The file's `<title>` should be sufficient to describe the scenario being

- tested.

* Asynchronous tests have a few subtleties.

* The `async_test` wrapper calls its function with a test case argument that

is used to signal when the test case is done, and to connect assertion

@@ -516,7 +510,6 @@ Below is an example of a fairly minimal test that uses a Blink-Specific API

```html

<!doctype html>

-<title>DOM: Event.isTrusted for UI events</title>

<meta name="assert"

« no previous file with comments | « no previous file | no next file » | no next file with comments »