You will be forking this project, performing the required modifications and submitting a pull request with your answers. Your pull request will not be merged. We will evaluate it and close the request. Any comments or questions we have will be given during a phone screening if the pull request meets our minimum standards.
Each phase of work is labeled with the applicable positions. Complete everything for the position you are interested in. Use a feature branch for all of your work.
Fork this project and do whatever you need to do to get the webapp running locally and the provided feature running and green.
Log any steps needed here:
- OS used:
Flesh out the scenario set for the calculator.
Ensure that all features are green.
The calculator is a tinker toy. Make it do something interesting.
The code should be well factored after you are done with it and there should be unit tests. Write about which unit testing framework you picked, how to test with it and why you picked it here:
Additionally, you must add sufficient feature coverage.
Question and Answer time. Fill in your answer in this file immediately following the question.
- What do the acronyms TDD, BDD, ATDD and SBE stand for?
- How do each of those relate to each other? Where do they originate?
- What is the fundamental value of SBE? How does it fit into an organization?
- What is the key defect in the provided feature?
- Compare and Contrast FitNesse, JBehave, RSpec and Cucumber. Identify strengths of and issues with each tool. If you have not used one of those tools before, substitute in a similar one and explain.
Question and Answer time. Fill in your answer in this file immediately following the question.
- What is Continuous Integration?
- How does that relate to Continuous Delivery?
- Detail your experiences with CI tools.
- Detail your experiences with ticket tracking tools.
- What is VCS? What is DVCS?
- Detail your experiences with version control tools.
- What is the difference between Feature Branching and Trunk-Based Development?
No content from your pull request will be used for any other purpose than determining your fitness as a candidate.
Submitting a pull request is an affirmative agreement that all work therein is original work by you unless otherwise explicitly cited. Work which is entirely the original content of other people should not be included. Failure to meet this obligation will result in disqualification.
This repository is licensed under the MIT License:
Copyright (c) 2013 Georgia Tech Research Institute
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.