{"push_id":1006699288,"size":7,"distinct_size":7,"ref":"refs/heads/master","head":"e60d0e0961fc7982b5ee600f16c5490ae4e02e14","before":"be781b5d8de1674effec425bf623b99347eac936","commits":[{"sha":"a2dec1432cc130bdb33816183c4bd262a1e786a0","author":{"email":"6e6aa02ae130e247dffae794e72292a226404666@me.com","name":"Jesse Gibson"},"message":"Add tests for the polyfill file, add function parsing for new direction\n\nSome major modifications are coming to panic. For one, it's been decided that there will be a test file that sends test instructions to a variable number of peers and performs checks across machines to ensure the data saved correctly. In order to relay the test instructions and have an easy, flexible test interface, it's been decided that eval will be used to send setup/test functions out to the peers (eval is horrible, we know. This is only for the test framework for browsers that opt into our stress-test DDOS network. I'm gonna stop talking now).","distinct":true,"url":"https://api.github.com/repos/PsychoLlama/panic/commits/a2dec1432cc130bdb33816183c4bd262a1e786a0"},{"sha":"3e4946951adde6f59c07074cc0bda52d8c5c2949","author":{"email":"6e6aa02ae130e247dffae794e72292a226404666@me.com","name":"Jesse Gibson"},"message":"Test coverage, imperative instead of declarative test syntax\n\nAfter discussing the goals for panic more with Mark and Sean, I decided to take panic in a different direction. Previously, the interface used an options object to do test setup, and was completely declarative in nature. In order to do more complex things with the framework, it would have needed new features hacked into the existing one, without a solid, well tested foundation to build on. That was a bit frightening. As radical as it was, I decided to mostly rewrite the framework to be similar to a traditional test framework (such as jasmine or mocha), with a major twist - it will send your tests out to the connected clients to be run, and you can filter which platforms/peer IDs to run on. Since the approach is more imperative, it will be more verbose, but it also allows for faster scaling, ease of adding new features, more expressive/flexible tests, greater coverage, and approachable syntax.\n\nWith luck, panic will be around for quite some time. If that's the case, it really, really needs high test coverage, so I began with jasmine from the start. In addition, who's going to trust results from an untested test framework?","distinct":true,"url":"https://api.github.com/repos/PsychoLlama/panic/commits/3e4946951adde6f59c07074cc0bda52d8c5c2949"},{"sha":"87332c088bb61269bf4b7cfb46d335fbb4d3cdad","author":{"email":"6e6aa02ae130e247dffae794e72292a226404666@me.com","name":"Jesse Gibson"},"message":"Add UID to each test, save test name when available\n\nEach test now has a unique ID to reference by. This will be useful for reporters and tracking of \"done\" events. Also, each test now saves the name it's been given.","distinct":true,"url":"https://api.github.com/repos/PsychoLlama/panic/commits/87332c088bb61269bf4b7cfb46d335fbb4d3cdad"},{"sha":"3081fbc9d6068b0c70f81d0e2a2ff2a64ecd86e1","author":{"email":"6e6aa02ae130e247dffae794e72292a226404666@me.com","name":"Jesse Gibson"},"message":"Add event emitter, always name tests\n\nCreated an event emitter instance for reporters and the test stack. Currently, the only event that fires is \"begin\".\n\nAll tests are now named, whether by their given name or as the name \"Anonymous\".","distinct":true,"url":"https://api.github.com/repos/PsychoLlama/panic/commits/3081fbc9d6068b0c70f81d0e2a2ff2a64ecd86e1"},{"sha":"fe0f9aabf5bb1ec29d83c43d6eb628984aeccc9e","author":{"email":"6e6aa02ae130e247dffae794e72292a226404666@me.com","name":"Jesse Gibson"},"message":"Restrict access to `bump`, begin client framework. All tests passing.\n\nThere were some race conditions involving the `bump` function, where some tests were failing because synchronous code was not acting as synchronous as it should (and I'm still not quite sure what's causing it). I've removed access to the bump function in the Test constructor (side note: none of the tests broke when I did, so apparently there was no coverage).\n\nThe client logic has been revised, as some of it was untested and wouldn't be useful for quite some time. I'm be starting with the context parser, then I'll be moving onto platform/ID filtering, then onto test runners/client context instances.","distinct":true,"url":"https://api.github.com/repos/PsychoLlama/panic/commits/fe0f9aabf5bb1ec29d83c43d6eb628984aeccc9e"},{"sha":"1f007c728f0d7567ff9c46e963ecd0d2c5696495","author":{"email":"6e6aa02ae130e247dffae794e72292a226404666@me.com","name":"Jesse Gibson"},"message":"Add callback list parser\n\nPass in an array of objects, with optional conditional expressions/functions, and get back a list of objects that passed the conditional and parsed properly as functions. It's in the format that the server test configuration constructor will send off to the client, so that instead of being terribly verbose, you can say `response.cbs = parse(response.cbs)` and get a validated list of test objects.","distinct":true,"url":"https://api.github.com/repos/PsychoLlama/panic/commits/1f007c728f0d7567ff9c46e963ecd0d2c5696495"},{"sha":"e60d0e0961fc7982b5ee600f16c5490ae4e02e14","author":{"email":"6e6aa02ae130e247dffae794e72292a226404666@me.com","name":"Jesse Gibson"},"message":"Add client Context constructor. All tests passing.\n\nAdded module for the \"this\" context that test runners will need. The constructor handles timeout settings, \"done\" callbacks, \"env\" variables (and merges), as well as basic input validation. It'll be used during tests as an interface to the exterior controls, like \"done\" events and iterables/progress reporters.","distinct":true,"url":"https://api.github.com/repos/PsychoLlama/panic/commits/e60d0e0961fc7982b5ee600f16c5490ae4e02e14"}]}