Feature:
As a non-attendee of CukeUp 2013
I want to read digested summaries of the talks
So that I can decide which presentations to watch
@aslak_hellesoy
Scenario: Keynote: The Cucumber Ecosystem
Given you are an experienced Cucumber user
When you are asked if Cucumber is a browser
automation tool
Then you should reply in the negative
But you should say that it works well with browser
automation tools such as Selenium
@mattwynne
Scenario: Why your step definitions should be one-liners and other pro tips
Given you have reviewed your existing test suite
When your feature file reads like instructions for
building flat-pack furniture
Then you should refactor it to be declarative rather
than imperative
@andrey.volkin
Scenario: Productive testing with Cucumber and JetBrains IDEs
Given you are using IntelliJ Ultimate Edition
When you open a project with Cucumber tests
Then you can benefit from Cucumber IDE integration
@jbpros
@mattwynne
Scenario: Hands-on introduction to Cucumber.js
Given you are writing a Noughts and Crosses game
in JavaScript
Then you can test its behaviour using Cucumber JS
@alan_parkinson
Scenario: Creating data with the Test Data Builder pattern
Given your tests require test data to be populated
as a prerequisite
Then you should create this data using the Test Data
Builder Pattern
And this data should be created through APIs
But not through SQL or UI manipulation
@mnacos
Scenario: Developing and testing Facebook apps
Given you are testing a Facebook app
When creating test data
Then you should use Koala
But be aware of limitations of testing Canvas apps
@sebrose
@without_ui
Scenario: Don't you trust me? (a technical approach to building trust and consensus)
Given you are working in an environment where there
is a lack of trust between testers and developers
When you use feature files as living documentation
And consider using tagged hooks (@without_ui) so that
the same test may be executed with UI
(in a browser) or without UI (as a Unit Test)
Then you can increase trust within
the development team
@meladiep
@msoeken
Scenario: Towards Automatic Scenario Generation Based on Uncovered Code
Given you want to improve your test coverage
When you do static analysis of your code
Then you can automatically generate Cucumber
scenarios based on uncovered code
But this tool's code is not yet released publicly