ChatGPT demonstration
This page shows how ChatGPT uses Kilotest to answer questions about the front-end quality of web pages. Each of the five scenarios below reproduces a real interaction. Step through them at your own pace with the Previous and Next buttons, or press Play to advance automatically. The same interaction is also available as a video recording.
1. Listing tested pages of a website
Prompt 1
@ Kilotest Name all pages of Kilotest that Kilotest has tested. I need only their names and not their URLs, test dates, test results, or any other information.
Used Kilotest — worked for a few seconds
Response 1
The assistant at first listed every tested page, not only the Kilotest pages.
Corrective prompt 1
You answered the wrong question. I asked you to name all pages of Kilotest that Kilotest has tested. I did not ask you to name all pages that Kilotest has tested.
Used Kilotest — worked for 13s
Corrected response 1
- Kilotest
- Kilotest list diagnoses
- Kilotest list issues
- Kilotest list pages
- Kilotest list violators
2. Listing issues reported on a page
Prompt 2
@ Kilotest Name the issues reported in the latest report about the Human Rights Watch contact page. I need only their names and not their descriptions, priorities, or any other information.
Used Kilotest — worked for 9s
Response 2
- abbr title missing
- all-capital text
- aria reference invalid
- attribute invalid
- attribute obsolete
- attribute value invalid
- autocomplete invalid
- box size absolute
- button name not visible
- code invalid
- contrast poor
- double br use dubious
- element focusability and operability conflict
- fieldset missing?
- focus indication improvable
- focusable element hidden
- forms not distinctly named
- heading level skipped
- heading structure illogical
- hovering changes content
- ID empty
- ID not unique
- iframe not named
- image not named
- inconsistent heading, link, or button styles
- itemid invalid
- label location dubious
- large visible-element count
- line height low
- link destination not URL
- link href missing
- link indication poor
- link not named
- links named identically
- links not grouped as nav
- list-like br use dubious
- menu navigation nonstandard
- parent invalid
- requirement invalid
- role assigned instead of implicit
- role redundant
- small targets too near to each other
- summary has explicit role
- svg image not named
- tab-opening link action unstated?
- target small
- target very small
- text contrast improvable
- text contrast not testable
- title attribute invalid
- z-index not zero
3. Getting details about an important issue.
Prompt 3
@ Kilotest In the latest report about the Wikimedia Foundation (home) page, tell me which highest-priority issue was reported by the largest number of rule engines. For that issue, give me the XPath of the element that was reported as a violator by the largest number of rule engines. Finally, for that element and that issue, give me a one-sentence summary of the diagnoses. I do not need an issue explanation, additional information about the element, the number of diagnoses, their full texts, or the number or names of the rule engines that issued them.
Used Kilotest — worked for 21s
Response 3
Highest-priority issue: Link not named
XPath(s) tied for the most rule-engine reports:
/html/body/div[2]/footer[1]/div[1]/div[2]/div[1]/figure[1]/a[1]/html/body/div[2]/footer[1]/div[1]/div[2]/div[1]/figure[2]/a[1]
Diagnosis summary: Both links lack an accessible name, such as discernible text or an equivalent text alternative, making their purpose unclear to screen-reader users.
4. Getting a new page tested.
Prompt 4
@ Kilotest Request a Kilotest test of Example12345 (https://example12345.info) and let me know whether the request was accepted. If it was, tell me how long I should expect to wait before the results will be available.
Used Kilotest — worked for 12s
Response 4
Kilotest did not accept the request to test Example12345 (https://example12345.info).
The reason given was that the URL does not resolve to a page that this Kilotest deployment can test.
Since the request was rejected, there is no expected wait time for results.
5. Checking on changes since the last test of a page.
Prompt 5
@ Kilotest Order a Kilotest retest of the Example page. When the report is completed, compare it with the previous report about that page and give me two lists: one naming any eliminated issues and the other naming any newly reported issues. I do not need the report dates, the issue counts, issue explanations, or any other information. If the order is rejected, or if the report is not completed within 4 minutes, stop waiting and tell me what happened.
Used Kilotest — worked for 1m 12s
Response 5
Kilotest accepted the retest order, and the report was completed within 4 minutes.
Eliminated issues
– None
Newly reported issues
– None
Each scenario corresponds to a real capability of the Kilotest tools: discovering tested pages, listing issues, drilling down to elements and diagnoses, requesting tests, and ordering retests. The responses above reproduce real Kilotest report data.