Blog Posts
Subscribe to the full blog feed using RSS
Interested in sponsoring the site? [find out more]
Subscribe to the full blog feed using RSS
This post and video shows how to complete the authentication failed with username and password challenge number 29, which returns a status code of 401.
TLDR; Can Test Automation mind defects? Yes, both regressions and new defects by adding more variation into the paths or data used.
Statements like “Test automation should-not/can-not/will-not find defects” do not completely match my experience. In my experience, Automated Execution can be used to help find defects and frequently does. Not just ‘regressions’ but ’new defects’ as well.
This post and video shows how to complete the status code challenges. Numbers 25, 26, 27, 28 which trigger the status codes 405, 500, 501 and 204.
This post and video shows how to complete the challenge POST /todos JSON to XML to send a POST request to create a todo item using JSON but receive XML response.
This post and video shows how to complete the challenge POST /todos XML to JSON to send a POST request to create a todo item using XML but receive JSON response.
This post and video shows how to complete the challenge POST /todos (415) to send a POST request to try and create a todo item but with unsupported content type.
This post and video shows how to complete the challenge POST /todos JSON to send a POST request to create a todo item with body and response in JSON format.
This post and video shows how to complete the challenge POST /todos XML to send a POST request to create a todo item with body and response in XML format.
This post and video shows how to complete the challenge GET /todos (406) to send a GET request for all todos but passing in an ‘accept’ format that the system does not support.
Asking questions like “Do we need testing?” are important. But there are other questions we should probably ask first.