Servirtium == Service Virtualized HTTP (for Java) in a record/playback style
Utilization of "Service Virtualization" is best practice towards fast and consistent test automation. This tech should be used in conjunction with JUnit/TestNG, etc. Versus alternate technologies, Servirtium utilizes Markdown for recorded HTTP conversations, which aids readability and diffing. Those are helpful when Service Virtualization is participating in a Technology Compatibility Kit
- By being a "man in the middle" it enables the recording of HTTP conversations and store them in Markdown under source-control co-located with the automated tests themselves.
- In playback, Servirtium allows the functionality tested in the service tests to be isolated from potentially flaky and unquestionably slower "down stack" and remote services.
- A diffable format to clearly show the differences between two recordings of the same conversation.
And this is just for Java teams. Non-Markdown alternates are:
- Mountebank by ThoughtWorker Brandon Byars for a more versatile SV solution (written in NodeJs, but usable from other languages).
- WireMock (more establised)
- Linkedin's Flashback (newer)
Not only is Servirtium just for Java teams wanting it is in the same process as the test-runner. It is not designed to be a standalone server.
What do recordings look like?
See ExampleSubversionCheckoutRecording.md which was recorded from a real Subversion 'svn' command line client doing it's thing, but thru Servirtium as a HTTP-proxy. After the recording of that, the replay side of Servirtium was able to pretend to be Apache+Subversion for a fresh 'svn checkout' command. This one was the recorder, and this one the replayer for that recorded conversation.
Java only for now, though usable in the broader JVM ecosystem. Ports to other languages is a direction I'd like to go in. Perhaps a rewrite in Rust, and then bindings back to Java, C#, Python, Ruby and NodeJs would be a more sustainable route long term.
The recorder isn't very good at handling parallel requests. Most of the things you want to test will be serial (and short) but if your client is a browser, then you should half expect for parallelized operations.
Servirtium can't yet listen on over HTTPS.
Servirtium can't yet function as a HTTP Proxy server. It must be a "man in the middle", meaning you have to be able to override the endpoints of services during JUnit/TestNG invocation in order to be able to record them (and play them back).
Some server technologies (like Amazon S3) sign payloads in a way that breaks for middle-man deployments. See S3.
Notable examples of use
SvnMerkleizer project - emulation of Subversion
Todobackend record and playback
Note: playback does not pass all the tests because there's a randomized GUID in the request payload that changes every time you run the test suite. It gets one third of the way through though.
Note: this limitation is being resolved, presently
Readiness for general industry by lovers of test automation?
Nearly ready, but still being actively worked on.
Servirtium's default listening port
As per the default port calculator for 'servirtium': 61417
This builds the binaries, but skips integration tests
mvn clean install
This builds the binaries, and includes integration tests (that use various services on the web)
mvn clean install -Ptests
License & Legal warning
BSD 2-Clause license (open source)
Be careful: your contracts and EULAs with service providers (as well as application/server makers for on-premises) might not allow you to reverse engineer their over-the-wire APIs.
A real case: Reverse engineering of competitor’s software cost company big - and you might say that such clauses are needed to prevent licensees from competing with the original company with arguably "stolen" IP.
We (test engineers) might morally think that we should be OK for this, as we're just doing it for test-automation purposes. No matter, the contracts that are signed often make no such distinction, but the case above was where the original maker of an API went after a company that was trying to make something for the same ecosystem without a commercial relation on that specifically.
Code of Conduct