This is not list of all features. See Configuration for complete information.
The result of pagewalker run is report like this. It's a standalone HTML/CSS/JavaScript page independent of Page Walker. You can browse it on local computer, send to someone, publish on your intranet. You can also easily integrate it with Jenkins (or other CI tools).
By default Chrome desktop is used for website browsing.
For testing mobile version of your website you have 2 options:
- Use DevTools mobile browser emulation with no additional configuration, add command line parameter:
--mobile-emulation yes - Run Chrome on physical device, see: Chrome on Android device
Running Chrome in headless mode keeps browser window invisible. You can run tests on remote server with no GUI out-of-the-box.
Feature called 2-step HTML validation
- First step: Validate raw HTML, original page source received from server.
- Second step: Validate HTML code exported from DOM after JavaScript execution. It saves errors that did not appear on first step. On most websites JavaScript modify page structure and now you can check if these changes are correct. You will also see that possible errors are related to JavaScript, because they did not occur on raw HTML.
For HTML validation Nu Html Checker (v.Nu) is used. The same library as used by W3C Markup Validator.
Run multiple instances of same Chrome browser in parallel (or different versions if you wish). Just run multiple pagewalker commands with different Chrome remote debugger port for every instance. If you run second instance with the same port number as already running, first instance will be stopped.
This feature helps collect more data and detect more bugs. When page is loaded, scrolling to the bottom of page occurs. This action can fire more JavaScript events, AJAX requests, show more images. It you don't like this idea, you can disable it.
By default Page Walker is finding links to other pages within domain and visiting them. When you have specific list of pages to visit in specific order, you can use it. Save this list in text file, one page per line. Every page is relative to domain. For URL http://example.com/login domain is http://example.com and page is /login. Provide path to this file in argument --pages-list.
Pay attention to --list-only argument.
- If set to
yes: only pages from list will be visited and no other pages. Option maximum number of pages to visit has no effect. - If set to
no: option maximum number of pages to visit is taken into account. After visiting pages from list, pages found automatically will be visited.
You can login in different ways:
- Provide HTTP Basic authentication credentials
- Fill in the login form using Initial actions
- Add Custom cookies with authentication tokens
See: Domain blacklist