Testing your applications is important! Writing good tests is just as important! This talk will be divided into two main parts. The first part will cover exactly what goes into a good test. The second part will cover the basics of two testing frameworks, OCDSpec and Objective C Slim. Objective C Slim is an acceptance testing framework, and for those of you familiar with Ruby and Rails, OCDSpec is a unit testing familiar with syntax inspired by Jasmine and Rspec. At the end of this talk, you should have no problem testing all of your future iOS applications.
Ember is a framework for creating ambitious web applications. Ambitious applications need tests. Although many find it difficult to weed through the various sources of information, it is possible to thoroughly test your Ember application today. We've aggregated the collective experiences, trials and errors regarding testing Ember applications from leaders in the Ember community to create The Unofficial, Official Ember Testing Guide. We'll walk through it live, cover specific testing scenarios and solve real testing dilemmas.
You'll leave this session knowing what to test, how to approach it with confidence, and the resources available to fall back on when you need it.
One of the greatest themes the Ruby community has embraced is testing. Countless words have been written, and tools coded, to make it as easy and painless as possible to write almost any kind of test imaginable. And yet despite all of the time we spend writing tests, we still end up with bugs in production, and we still curse our test suites for being too large, too slow, or too complicated.
Managing your infrastructure with configuration management tools like Chef melds the practices of development and operations together. This workshop will focus on a development practice - Test Driven Development - and how that method can be applied to managing your Rails infrastructure and deployments. You will learn how to: Analyze your application and define your infrastructure needs (databases, load balancers, etc.), define unique infrastructure requirements for Rails applications (i.e. asset pipeline), capture your requirements in tests using Test Kitchen, ServerSpec, and other frameworks
Your app is a unique snowflake. Your tests are too… but they shouldn't be!
Years helping teams write better tests has taught me one thing: consistency is crucial. Inconsistent tests slow teams down, wasting time to understand how each test works. Deciding on conventions—even arbitrary ones—can prevent tremendous pain later.
This talk will introduce a ready-to-fork Test Style Guide of carefully-considered rules and templates for Rubyists. You can customize it to fit your preferred tools, too. Soon, you'll be on your way to having more consistent tests that are much more fun to maintain!
There is a value in writing tests and there is also a cost. The currency is time. The trade-offs are difficult to evaluate because the cost and value are often seen by different people. The writer of the test bears much of the short term cost while long term benefits and cost are borne by the rest of the team. By planning around both the the cost and value of your tests, you’ll improve your tests and your code. How much do slow tests cost? When is it worth it to test an edge case? How can you tell if testing is helping? Here are some strategies to improve your tests and code.