Pinboard (jm)
https://pinboard.in/u:jm/public/
recent bookmarks from jmTesting@LMAX – Time Travel and the TARDIS2016-11-21T11:29:55+00:00
https://www.symphonious.net/2014/04/01/testinglmax-time-travel-and-the-tardis/
jmlmax testing system-tests acceptance-tests tests timehttps://pinboard.in/https://pinboard.in/u:jm/b:0c1c1fc4c02e/CD at LMAX: Testing into Production and Back Again2016-05-11T22:21:47+00:00
http://www.infoq.com/presentations/cd-lmax
jmtesting lmax build test continuous-delivery devhttps://pinboard.in/https://pinboard.in/u:jm/b:b59f1ca68a2c/Low-latency journalling file write latency on Linux2015-12-09T14:58:39+00:00
http://epickrram.blogspot.co.uk/2015/12/journalling-revisited.html
jmlinux xfs ext3 ext4 filesystems lmax performance latency journalling opshttps://pinboard.in/https://pinboard.in/u:jm/b:9b225ebb15c4/Testing@LMAX – Aliases2015-06-08T10:20:49+00:00
https://www.symphonious.net/2015/06/08/testinglmax-aliases/
jmCreating a user with our DSL looks like: registrationAPI.createUser("user");
You might expect this to create a user with the username ‘user’, but then we’d get conflicts between every test that wanted to call their user ‘user’ which would prevent tests from running safely against the same deployment of the exchange.
Instead, ‘user’ is just an alias that is only meaningful while this one test is running. The DSL creates a unique username that it uses when talking to the actual system. Typically this is done by adding a postfix so the real username is still reasonably understandable e.g. user-fhoai42lfkf.
Nice approach -- makes sense.
]]>testing lmax system-tests naming codinghttps://pinboard.in/https://pinboard.in/u:jm/b:f785d985512e/Performance Testing at LMAX2015-06-03T12:49:58+00:00
http://epickrram.blogspot.co.uk/2014/05/performance-testing-at-lmax-part-one.html
jmperformance testing tests simulation latency lmax trading sniffing packet-capturehttps://pinboard.in/https://pinboard.in/u:jm/b:c962c123de77/Making End-to-End Tests Work2015-05-08T10:43:28+00:00
https://www.symphonious.net/2015/04/30/making-end-to-end-tests-work/
jmend-to-end testing acceptance-tests tests system-tests lmaxhttps://pinboard.in/https://pinboard.in/u:jm/b:2f546a981ba9/InfoQ: Lock-free Algorithms2012-04-30T16:07:47+00:00
http://www.infoq.com/presentations/Lock-free-Algorithms
jmlock-free locking mutexes algorithms lmax disruptor infoq slides presentations qcon javahttps://pinboard.in/https://pinboard.in/u:jm/b:8b73716da342/