mdbook/tests/gui/sidebar-active.goml

// This GUI test checks the active page sidebar highlight.

go-to: |DOC_PATH| + "test_book/index.html"

assert-text: ("mdbook-sidebar-scrollbox a.active", "Prefix Chapter")

go-to: |DOC_PATH| + "test_book/individual/index.html"

assert-text: ("mdbook-sidebar-scrollbox a.active", "3. Markdown Individual tags")

go-to: |DOC_PATH| + "test_book/index.html?highlight=test"

assert-text: ("mdbook-sidebar-scrollbox a.active", "Prefix Chapter")

go-to: |DOC_PATH| + "test_book/individual/index.html?highlight=test"

assert-text: ("mdbook-sidebar-scrollbox a.active", "3. Markdown Individual tags")
Break off query string when comparing url for sidebar 2025-04-21 12:03:17 -07:00			`// This GUI test checks the active page sidebar highlight.`

Support multiple books in the GUI tests This adds the ability to use multiple books for the GUI tests. This is helpful since some tests need special configuration, and sharing the same book can make it difficult or impossible to test different configurations. It also makes it difficult to make changes to the test_book since it can affect other tests. This works by placing the books in the tests/gui/books directory. The test runner will automatically build all the books. The gui tests can then just access the DOC_PATH with the name of the book. Books are now saved in a temp directory to make it easier to use the DOC_PATH variable, instead of being tests/gui/books/book_name/book which is a little awkward. Following commits will restructure the existing book. This is just a mechanical move. 2025-10-13 20:07:38 -07:00			`go-to: \|DOC_PATH\| + "test_book/index.html"`
Break off query string when comparing url for sidebar 2025-04-21 12:03:17 -07:00
			`assert-text: ("mdbook-sidebar-scrollbox a.active", "Prefix Chapter")`

Support multiple books in the GUI tests This adds the ability to use multiple books for the GUI tests. This is helpful since some tests need special configuration, and sharing the same book can make it difficult or impossible to test different configurations. It also makes it difficult to make changes to the test_book since it can affect other tests. This works by placing the books in the tests/gui/books directory. The test runner will automatically build all the books. The gui tests can then just access the DOC_PATH with the name of the book. Books are now saved in a temp directory to make it easier to use the DOC_PATH variable, instead of being tests/gui/books/book_name/book which is a little awkward. Following commits will restructure the existing book. This is just a mechanical move. 2025-10-13 20:07:38 -07:00			`go-to: \|DOC_PATH\| + "test_book/individual/index.html"`
Break off query string when comparing url for sidebar 2025-04-21 12:03:17 -07:00
			`assert-text: ("mdbook-sidebar-scrollbox a.active", "3. Markdown Individual tags")`

Support multiple books in the GUI tests This adds the ability to use multiple books for the GUI tests. This is helpful since some tests need special configuration, and sharing the same book can make it difficult or impossible to test different configurations. It also makes it difficult to make changes to the test_book since it can affect other tests. This works by placing the books in the tests/gui/books directory. The test runner will automatically build all the books. The gui tests can then just access the DOC_PATH with the name of the book. Books are now saved in a temp directory to make it easier to use the DOC_PATH variable, instead of being tests/gui/books/book_name/book which is a little awkward. Following commits will restructure the existing book. This is just a mechanical move. 2025-10-13 20:07:38 -07:00			`go-to: \|DOC_PATH\| + "test_book/index.html?highlight=test"`
Break off query string when comparing url for sidebar 2025-04-21 12:03:17 -07:00
			`assert-text: ("mdbook-sidebar-scrollbox a.active", "Prefix Chapter")`

Support multiple books in the GUI tests This adds the ability to use multiple books for the GUI tests. This is helpful since some tests need special configuration, and sharing the same book can make it difficult or impossible to test different configurations. It also makes it difficult to make changes to the test_book since it can affect other tests. This works by placing the books in the tests/gui/books directory. The test runner will automatically build all the books. The gui tests can then just access the DOC_PATH with the name of the book. Books are now saved in a temp directory to make it easier to use the DOC_PATH variable, instead of being tests/gui/books/book_name/book which is a little awkward. Following commits will restructure the existing book. This is just a mechanical move. 2025-10-13 20:07:38 -07:00			`go-to: \|DOC_PATH\| + "test_book/individual/index.html?highlight=test"`
Break off query string when comparing url for sidebar 2025-04-21 12:03:17 -07:00
			`assert-text: ("mdbook-sidebar-scrollbox a.active", "3. Markdown Individual tags")`