About Stack-In-A-Box¶
StackInABox started out of trying to reduce code in tests. Initially Mock was used. That proved problematic as it was hard to get the the mock.patch applied correctly for third-party tooling (e.g OpenStack Keystone Client) that didn’t break due to changes upstream or even in minor changes in the test. The tests were then moved to use HTTPretty which brought a lot of stability and all was good until one looked at how much code was being copy/pasted between tests to use the tool. In centralizing the code and abstracting it in a way that worked for all the tests Stack-In-A-Box was born. Since then additional support tools ( RequestsMock, Response ) have been added.