Effective business communication heightens productivity. An important step in increasing communication and decreasing inefficiencies is to eliminate assumptions.
By iterating with the business using Behavior Driven Development tools like Cucumber, we’re able to account for discrepancies in interpretations and speed up the development process over the long term while allowing changing requirements from the business.
Two best practices that have gained a lot of traction over the last years in software development are Continuous Integration and Continuous Deployment. Read about their benefits and how you can start using them in this article.
Bogus verifies that you only stub real method calls. There must be a context in which the stubbed method acts the way you stubbed it, or Bogus will fail your tests. Therefore Bogus checks the contract between mocked components – something that you would usually use integration tests for.
Traditionally application code is written first and tests afterwards. After writing a piece of code, you write unit tests. And once you finished a few pieces of code, you write integration tests to see if they fit together. In Behavior-Driven development there is an approach called Outside-In Development where we go the other way round. Have a look at this screencast to learn more!
When writing software tests, you usually need to get your application into a certain state by creating test data. This test data is the basis to run your tests on. In this screencast you will learn about the test data generation tool factory_girl.
Once you get started with Cucumber, the question is how to write your features. How can you keep your features maintainable so you don’t have to correct them after each change in the application? How can you reuse steps most efficiently? What are typical Cucumber smells?
Following is a list of 5 best practices that can help in your daily Cucumber life.
In this screencast we look at the two Selenium tools Selenium IDE and Selenium WebDriver. Selenium is a remote control for your browser. Selenium lets you perform browser actions by creating scripts instead of using your mouse or keyboard. Let's have a look!
Continuous Integration and Deployment speeds up your workflow tremendously. In this screencast we will deploy our Ruby on Rails app to Heroku. Hosted testing and automated deployment is provided by the Codeship. Learn more!
When starting with continuous integration and deployment, code coverage is one of the tools that improve your workflow significantly.
Being able to quickly grasp which parts of your application aren't well tested is incredibly important. Especially tracking your code coverage over time is a powerful feature.
Test-driven development focuses on the developer's opinion on how parts of the software should work. Behavior-driven development focuses on the users' opinion on how they want your application to behave.