{"push_id":3127170800,"size":2,"distinct_size":2,"ref":"refs/heads/unittest-rpminjection","head":"9fe8ec611ff8a0d1628aea1534d8ae13fe3915e5","before":"c7ee281935d8dcdad924beb1b31acabd83979a88","commits":[{"sha":"8aaa207cce5628bfddb97ae77458c9c7b4e2cb75","author":{"name":"Petr Muller","email":"ea1dce70351cdada45108343dcffcd9084bc150d@redhat.com"},"message":"Refactor testing code\n\n- Clean up the mess in import naming and ordering\n- Extract and refactor ciopTestingClient so that all clientsets are\n  always created and the step testing methods just obtain those they need.\n  This makes step testing methods simpler.","distinct":true,"url":"https://api.github.com/repos/petr-muller/ci-operator/commits/8aaa207cce5628bfddb97ae77458c9c7b4e2cb75"},{"sha":"9fe8ec611ff8a0d1628aea1534d8ae13fe3915e5","author":{"name":"Petr Muller","email":"ea1dce70351cdada45108343dcffcd9084bc150d@redhat.com"},"message":"Unit tests: RPMImageInjectionStep\n\nThis step is the first from the unit-tested to use Routes and Builds, so\nfake clientsets needed to be added for these resources. Testing the step\nis straightforward and uses the established setup-examine-execute\npattern. This step depends on Builds having correct behavior (not just\nBuild resource having correct status at the end, but also creating the\nOutput, in this case an ImageStreamTag), so fake cluster behavior is\nmore complicated. This behavior is likely to be useful for testing more\nsteps, so it was extracted into a separate method in testing.go.","distinct":true,"url":"https://api.github.com/repos/petr-muller/ci-operator/commits/9fe8ec611ff8a0d1628aea1534d8ae13fe3915e5"}]}
{"actor":{"display_login":"petr-muller"}}