39b90a5f6e
It's misleading. The main heading sometimes isn't an fully qualified name at all. It's also redundant. It's always a child of `div.main-heading`, so just use that.
20 lines
1010 B
Plaintext
20 lines
1010 B
Plaintext
// This test ensures that the "go_to_first" feature is working as expected.
|
|
|
|
// First, we check that the first page doesn't have the string we're looking for to ensure
|
|
// that the feature is changing page as expected.
|
|
goto: "file://" + |DOC_PATH| + "/test_docs/index.html"
|
|
assert-text-false: (".main-heading h1", "Struct test_docs::Foo")
|
|
|
|
// We now check that we land on the search result page if "go_to_first" isn't set.
|
|
goto: "file://" + |DOC_PATH| + "/test_docs/index.html?search=struct%3AFoo"
|
|
// Waiting for the search results to appear...
|
|
wait-for: "#search-tabs"
|
|
assert-text-false: (".main-heading h1", "Struct test_docs::Foo")
|
|
// Ensure that the search results are displayed, not the "normal" content.
|
|
assert-css: ("#main-content", {"display": "none"})
|
|
|
|
// Now we can check that the feature is working as expected!
|
|
goto: "file://" + |DOC_PATH| + "/test_docs/index.html?search=struct%3AFoo&go_to_first=true"
|
|
// Waiting for the page to load...
|
|
wait-for-text: (".main-heading h1", "Struct test_docs::Foo")
|