Behaviour-driven / test-driven development
"Writing tests before writing code" sounds counter-intuitive at first. But TDD is really about design, not testing. Behaviour-driven development is an evolution of this process, where you think about the code in terms of how it must behave, not what tests it must pass. The benefits of BDD are
- code that meets more requirements first time
- less time wasted on debugging and rework
- less time wasted on unnecessary code
- fewer bugs making it out to end users
To be confident that the code will continue to behave correctly requires the correct use of unit and integration testing frameworks.
Habitable code
An agile team shares responsibility for delivering software. As a developer, you don't want features you are working on yourself to be held up by fixing or refactoring other people's work
PatchSpace encourages teams to use the best possible object-oriented design and architecture to keep the code maintainable. We offer assistance with design and refactoring to make this possible.
Continuous integration, automated deployment
PatchSpace believes that as much mundane work as possible should be automated. This is less prone to human error, and frees your time to do fun stuff instead, like build new features.
Continuous integration puts a server to work testing that your code builds, passes its associated tests, and deploys to a staging environment. PatchSpace can help assemble an integration environment to suit your project, and make sure it always has its green light on. From there, we can help tune your deployment scripts so that releasing a new version of your app is like pushing a button.