I created supporting videos for some of the chapters and sections in the book. These make most sense when read in conjunction with the book but offer a visual insight into tools used which the book can't cover quite as well.
Installing Tracks using Docker
Installing Tracks and using a virtual machine
An overview of Tracks GUI
Installing cURL for Windows
An overview of REST interaction with CURL
Using HTTP Debug Proxies as part of your REST testing
Using HTTP Debug Proxies with Docker and Localhost
Using HTTP Debug Proxies as Fuzzers to Create Data
An overview of the Postman GUI client
Using Postman GUI Client with an HTTP Proxy
Installing and Using the Java Source Code
Installing Tracks Via Docker
This is easy to install using Docker and this video shows the process in action.
Run mvn clean test in the unzipped folder to download the dependencies
Open the pom.xml in IntelliJ
Accessing tracks from the VM
Change the config in TestEnvDefaults
Running test data setup tests in SetupTracksTestDataUtilityTest
And I discuss how to can resolve some common setup issues
Other Blog posts and information you might want to read related to the material in the book,
I include a lot of extra references in the book, but these were found after publication and I
did not want to keep adding more links into the book, so I added them here instead, I also included a few from the book:
Ebook on sale at leanpub has had the following releases:
first release of the ebook
second release of the ebook
fixed some grammar errors throughout text
fixed spelling errors found throughout text
added an example in the "cURL Summary" chapter
added an introduction chapter "Introduction to APIs" on various web terminology - what is HTTP, what is an API, what is REST, what are HTTP headers, etc.
expanded text in "Exploring The Tracks API with cURL through a Proxy"
expanded text in chapter "Exploring Tracks API with Postman REST Client", added info on using with Proxy for Mac
added 'Summary' to end most chapters
split introduction into 3 chapters to allow for the API introduction
expanded the cURL case study chapter to have more information on cURL and what it is for, rather than diving straight into the technical stuff
added more explanatory notes in the cURL chapter "Case Study Example Using cURL on Tracks"
added a new chapter providing an overview of the Tracks 2.3.0 testing before diving into the details "The Case Study Overview - Testing Tracks v 2.3.0"
added A new chapter, with a new package in the code, covering JSON and XML processing with REST Assured "REST Assured JSON and XML Processing"
expanded the summary chapter on REST Assured "Summary of REST Assured" to cover serializing and deserializing
about 50 new pages of material added
additional grammar and spelling errors fixed throughout
increased dpi of images in readiness for paperback edition
split the 'sample code' chapter out of the 'install' chapter and moved to immediately before the 'starting to automate' chapter
paperback edition on hold until I amend the install and VM chapter to cater for bitnami discontinued VMs
Paperback edition currently in proof creation and review mode. Will be the same as the 2017/07/03 release.
On 4th August 2017 I was told that Bitnami had discontinued the Tracks VM and self contained install.
This is unfortunate as I found it the most reliable and easiest way of getting started. Turnkey is now the simplest way of getting started.
I emailed Bitnami, just in case they could reinstate the installs but on 8th August I learned that the installs would not be reinstated. I suspect the following links will forever remain 'discontinued'.
Stas Wasserman was kind enough to describe some additional information and workarounds on the Turnkey install:
The option of using Turnkey is available, with a minor, but quite annoying issue in Tracks UI.
(I know, the problem is not related to API, but it makes Tracks UI exploration a bit puzzling)
This issue is with missing icons in Tracks from Turnkey. For example, the start and the edit icons are missing for existing actions in a project (you can see the missing resources error in a browser dev console).