learn-xcpretty 0.1.11

data/features/html_report.feature

@@ -0,0 +1,40 @@
+Feature: Creating a HTML test report
+
+    Background:
+        Given the tests have started running
+
+    Scenario: Showing a test suite
+        Given I have a passing test in my suite
+        When I pipe to xcpretty with "--report html"
+        Then I should see a test suite section in HTML
+
+    Scenario: Showing failed tests
+        Given I have a failing test in my suite
+        When I pipe to xcpretty with "--report html"
+        Then I should see a failed test in HTML
+        And the failure counter should show 1 test
+
+    Scenario: Showing passing tests
+        Given I have a passing test in my suite
+        When I pipe to xcpretty with "--report html"
+        Then I should see a passing test in HTML
+
+    Scenario: Counting tests
+        Given I have a passing test in my suite
+        And I have a failing test in my suite
+        And the test suite has finished
+        When I pipe to xcpretty with "--report html"
+        Then I should see 2 tests in HTML
+
+    Scenario: Having many test classes
+        Given I have tests in my suite from 2 classes
+        When I pipe to xcpretty with "--report html"
+        Then I should see 2 test suite sections in HTML
+
+    Scenario: Writing to a custom file path
+        When I pipe to xcpretty with "--report html" and specify a custom path
+        Then I should have a test report in a custom path
+
+    Scenario: Writing to multiple custom file paths
+        When I pipe to xcpretty with two custom "html" report paths
+        Then I should have test reports in two custom paths

data/features/json_compilation_database_report.feature

@@ -0,0 +1,21 @@
+Feature: Create a JSON compilation database
+
+	Scenario: Showing file compilation
+        Given I have a file to compile
+        When I pipe to xcpretty with "--report json-compilation-database" and specify a custom path
+        Then the JSON compilation database should contain an entry with a command
+        Then the JSON compilation database should contain an entry with a directory
+        Then the JSON compilation database should contain an entry with a file
+
+    Scenario: Handling a complete xcodebuild session
+    	Given some big input
+    	When I pipe to xcpretty with "--report json-compilation-database" and specify a custom path
+    	Then the JSON compilation database should be complete
+
+    Scenario: Writing to a custom file path
+        When I pipe to xcpretty with "--report json-compilation-database" and specify a custom path
+        Then I should have a JSON compilation database in a custom path
+
+    Scenario: Writing to multiple custom file paths
+        When I pipe to xcpretty with two custom "json-compilation-database" report paths
+        Then I should have JSON compilation databases in two custom paths

data/features/junit_report.feature

@@ -0,0 +1,44 @@
+Feature: Creating a JUnit test report
+
+    Background:
+        Given the tests have started running
+
+    Scenario: Showing a test suite
+        Given I have a passing test in my suite
+        When I pipe to xcpretty with "--report junit"
+        Then I should see a test suite node
+
+    Scenario: Showing pending test output
+        Given I have a pending test in my suite
+        When I pipe to xcpretty with "--report junit"
+        Then I should see a pending test node in my report
+
+    Scenario: Showing failed tests
+        Given I have a failing test in my suite
+        When I pipe to xcpretty with "--report junit"
+        Then I should see a failed test node in my report
+
+    Scenario: Showing passing tests
+        Given I have a passing test in my suite
+        When I pipe to xcpretty with "--report junit"
+        Then I should see a passing test node in my report
+
+    Scenario: Counting tests
+        Given I have a passing test in my suite
+        And I have a failing test in my suite
+        And the test suite has finished
+        When I pipe to xcpretty with "--report junit"
+        Then I should see 2 tests in my report
+
+    Scenario: Having many test classes
+        Given I have tests in my suite from 2 classes
+        When I pipe to xcpretty with "--report junit"
+        Then I should see 2 test suites
+
+    Scenario: Writing to a custom file path
+        When I pipe to xcpretty with "--report junit" and specify a custom path
+        Then I should have a test report in a custom path
+
+    Scenario: Writing to multiple custom file paths
+        When I pipe to xcpretty with two custom "junit" report paths
+        Then I should have test reports in two custom paths

data/features/knock_format.feature

@@ -0,0 +1,11 @@
+Feature: Showing Knock-style test output
+
+    Scenario: Showing failed tests
+        Given I have a failing test in my suite
+        When I pipe to xcpretty with "--knock"
+        Then I should see text beginning with "not ok"
+
+    Scenario: Showing passing tests
+        Given I have a passing test in my suite
+        When I pipe to xcpretty with "--knock"
+        Then I should see text beginning with "ok"

data/features/simple_format.feature

@@ -0,0 +1,172 @@
+Feature: Showing build output in simple format
+
+    Scenario: Showing file compilation
+        Given I have a file to compile
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful compilation message
+
+    Scenario: Showing xib compilation
+        Given I have a xib to compile
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful compilation message
+
+    Scenario: Showing precompilation
+        Given I have a precompiled header
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful precompilation message
+
+    Scenario: Showing file compilation with color
+        Given I have a file to compile
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a yellow completion icon
+
+    Scenario: Showing xib compilation with color
+        Given I have a xib to compile
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a yellow completion icon
+
+    Scenario: Showing precompilation
+        Given I have a precompiled header
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a yellow completion icon
+
+    Scenario: Showing analyze
+        Given I have a file to analyze
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful analyze message
+
+    Scenario: Showing shallow analyze
+        Given I have a file to shallow analyze
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful analyze message
+
+    Scenario: Showing tiff file validation
+        Given I have a tiff file to validate
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful tiff validation message
+
+    Scenario: Showing touch file
+        Given I have a file to touch
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful touch message
+
+    Scenario: Showing analyze with color
+        Given I have a file to analyze
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a yellow completion icon
+
+    Scenario: Showing shallow analyze with color
+        Given I have a file to shallow analyze
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a yellow completion icon
+
+    Scenario: Showing tiff file validation with color
+        Given I have a tiff file to validate
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a yellow completion icon
+
+    Scenario: Showing touch file with color
+        Given I have a file to touch
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a yellow completion icon
+
+    Scenario: Showing the start of a test run
+        Given the tests have started running
+        When I pipe to xcpretty with "--simple"
+        Then I should see that test suite has started
+
+    Scenario: Showing the start of a test suite
+        Given I start a test suite
+        When I pipe to xcpretty with "--simple"
+        Then I should see the name of suite only
+
+    Scenario: Showing the end of a test suite
+        Given the test suite has finished
+        When I pipe to xcpretty with "--simple"
+        Then I should see that the test suite finished
+
+    Scenario: Showing failed test output
+        Given I have a failing test in my suite
+        And the test suite has finished
+        When I pipe to xcpretty with "--simple"
+        Then I should see the name of a failed test
+        And I should see the path of a failed test
+
+    Scenario: Showing successful test output
+        Given I have a passing test in my suite
+        When I pipe to xcpretty with "--simple"
+        Then I should see the name of a passing test
+        And I should not see the name of the test group
+        And I should not see the path of a passing test
+
+    Scenario: Colorizing slow-ish tests in yellow
+        Given I have a slow-ish test in my suite
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see the test time in yellow
+
+    Scenario: Colorizing slow tests in red
+        Given I have a slow test in my suite
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see the test time in red
+
+    Scenario: Showing pending test output
+        Given I have a pending test in my suite
+        When I pipe to xcpretty with "--simple"
+        Then I should see the name of a pending test
+
+    Scenario: Showing failed test output with color
+        Given I have a failing test in my suite
+        And the test suite has finished
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a red failed test mark
+        And the final execution message should be red
+
+    Scenario: Showing successful test output with color
+        Given I have a passing test in my suite
+        And the test suite has finished
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a green passing test mark
+
+    Scenario: Running tests without UTF-8 support
+        Given I have a passing test in my suite
+        And I pipe to xcpretty with "--no-utf --color"
+        Then I should see a non-utf prefixed output
+
+    Scenario: Showing code signing
+        Given I have a file to code sign
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful code signing message
+
+    Scenario: Showing code signing a framework
+        Given I have a framework to code sign
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful code signing message
+
+    Scenario: Showing preprocess
+        Given I have a file to preprocess
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful preprocessing message
+
+    Scenario: Showing a PBXCp copy
+        Given I have a file to copy with PBXCp
+        When I pipe to xcpretty with "--simple"
+        Then I should see a successful copying message
+
+    Scenario: Build fails when Pod install hasn't been run
+        Given podfile.lock wasn't in sync
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a red error message
+
+    Scenario: Compilation fails because of syntax errors
+        Given there was a syntax error
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see a red compilation error
+        And I should see a failed line
+        And I should see a cyan cursor
+
+    Scenario: Linker fails with undefined symbols
+        Given the linker has failed with undefined symbols
+        When I pipe to xcpretty with "--simple --color"
+        Then I should see the undefined symbold message
+        And I should see the symbol and reference that caused failure
+

data/features/steps/formatting_steps.rb

@@ -0,0 +1,268 @@
+# encoding: utf-8
+Given(/^I have a file to compile$/) do
+  add_run_input SAMPLE_COMPILE
+end
+
+Given(/^I have a xib to compile$/) do
+  add_run_input SAMPLE_COMPILE_XIB
+end
+
+Given(/^I have a precompiled header$/) do
+  add_run_input SAMPLE_PRECOMPILE
+end
+
+Given(/^I have a file to analyze$/) do
+  add_run_input SAMPLE_ANALYZE
+end
+
+Given(/^I have a file to shallow analyze$/) do
+  add_run_input SAMPLE_ANALYZE_SHALLOW
+end
+
+Given(/^I have a failing test in my suite$/) do
+  add_run_input SAMPLE_OLD_SPECTA_FAILURE
+end
+
+Given(/^all of my tests will pass in my suite$/) do
+  3.times { add_run_input SAMPLE_OCUNIT_TEST }
+end
+
+Given(/^I have a passing test in my suite$/) do
+  add_run_input SAMPLE_OCUNIT_TEST
+end
+
+Given(/^I have a slow\-ish test in my suite$/) do
+  add_run_input SAMPLE_SLOWISH_TEST
+end
+
+Given(/^I have a slow test in my suite$/) do
+  add_run_input SAMPLE_SLOW_TEST
+end
+
+Given(/^the tests have started running$/) do
+  add_run_input SAMPLE_OCUNIT_TEST_RUN_BEGINNING
+end
+
+Given(/^I start a test suite$/) do
+  add_run_input SAMPLE_OCUNIT_SUITE_BEGINNING
+end
+
+Given(/^the test suite has finished$/) do
+  add_run_input SAMPLE_OCUNIT_SUITE_COMPLETION
+  add_run_input SAMPLE_EXECUTED_TESTS
+end
+
+Given(/^I have a file to code sign$/) do
+  add_run_input SAMPLE_CODESIGN
+end
+
+Given(/^I have a framework to code sign$/) do
+  add_run_input SAMPLE_CODESIGN_FRAMEWORK
+end
+
+Given(/^I have a file to preprocess$/) do
+  add_run_input SAMPLE_PREPROCESS
+end
+
+Given(/^I have a file to copy with PBXCp/) do
+  add_run_input SAMPLE_PBXCP
+end
+
+Given(/^podfile.lock wasn't in sync$/) do
+  add_run_input SAMPLE_PODS_ERROR
+end
+
+Given(/^there was a syntax error$/) do
+  add_run_input SAMPLE_COMPILE_ERROR
+end
+
+Given(/^the linker has failed with undefined symbols$/) do
+  add_run_input SAMPLE_UNDEFINED_SYMBOLS
+end
+
+Given(/^I have a pending test in my suite$/) do
+  add_run_input SAMPLE_PENDING_KIWI_TEST
+end
+
+Given(/^I have a tiff file to validate$/) do
+  add_run_input SAMPLE_TIFFUTIL
+end
+
+Given(/^I have a file to touch$/) do
+  add_run_input SAMPLE_TOUCH
+end
+
+Then(/^I should see text beginning with "(.*?)"$/) do |text|
+  run_output.lines.to_a.detect {|line| line.start_with? text }.should_not be_nil
+end
+
+Then(/^I should see text containing "(.*?)" and beginning with "(.*?)"$/) do |inner, start|
+  run_output.lines.to_a.detect {|line| line.start_with?(start) && line.include?(inner)}.should_not be_nil
+end
+
+Then(/^I should (green|red) text beginning with "(.*?)"$/) do |color, text|
+  run_output.should start_with(send(color.to_sym, text))
+end
+
+Then(/^I should see a successful tiff validation message$/) do
+  run_output.should start_with("▸ Validating")
+end
+
+Then(/^I should see a successful touch message$/) do
+  run_output.should start_with("▸ Touching")
+end
+
+When(/^I pipe to xcpretty with "(.*?)"$/) do |flags|
+  run_xcpretty(flags)
+end
+
+When(/^I pipe to xcpretty with a custom formatter$/) do
+  formatter_path = File.expand_path('../../../spec/fixtures/custom_formatter.rb', __FILE__)
+  run_xcpretty("-f #{formatter_path}")
+end
+
+Then(/^I should see a custom compilation message$/) do
+  run_output.should start_with("😎 Compilation party time")
+end
+
+Then(/^I should see a successful compilation message$/) do
+  run_output.should start_with("▸ Compiling")
+end
+
+Then(/^I should see a successful precompilation message$/) do
+  run_output.should start_with("▸ Precompiling")
+end
+
+Then(/^I should see a successful analyze message$/) do
+  run_output.should start_with("▸ Analyzing")
+end
+
+Then(/^I should see a successful code signing message$/) do
+  run_output.should start_with("▸ Signing")
+end
+
+Then(/^I should see a successful preprocessing message$/) do
+  run_output.should start_with("▸ Preprocessing")
+end
+
+Then(/^I should see a successful copying message$/) do
+  run_output.should start_with("▸ Copying")
+end
+
+Then(/^I should see a yellow completion icon$/) do
+  run_output.should start_with(yellow("▸"))
+end
+
+Then(/^I should see a failed test icon$/) do
+  run_output.should start_with("F")
+end
+
+Then(/^I should see a passing test icon in ASCII$/) do
+  run_output.should start_with(".")
+end
+
+Then(/^I should see a red failed test icon$/) do
+  run_output.should include(red("F"))
+end
+
+Then(/^I should see a pending test icon in ASCII$/) do
+  run_output.should start_with("P")
+end
+
+Then(/^I should see a yellow pending test icon$/) do
+  run_output.should start_with(yellow("P"))
+end
+
+Then(/^the final execution message should be (red|green)$/) do |color|
+  last_line = run_output.lines.to_a.last
+  last_line.should be_colored(color.to_sym)
+end
+
+Then(/^I should see a green passing test icon$/) do
+  run_output.should include(green("."))
+end
+
+Then(/^I should see the name of a failed test$/) do
+  run_output.should =~ FAILING_TEST_NAME_MATCHER
+end
+
+Then(/^I should see the path of a failed test$/) do
+  run_output.should =~ TEST_PATH_MATCHER
+end
+
+Then(/^I should see the name of a passing test$/) do
+  run_output.should =~ PASSING_TEST_NAME_MATCHER
+end
+
+Then(/^I should not see the path of a passing test$/) do
+  run_output.should_not =~ TEST_PATH_MATCHER
+end
+
+Then(/^I should see that test suite has started$/) do
+  run_output.should =~ TEST_RUN_START_MATCHER
+end
+
+Then(/^I should see the name of suite only$/) do
+  run_output.should =~ TEST_SUITE_START_MATCHER
+end
+
+Then(/^I should see that the test suite finished$/) do
+  run_output.strip.should =~ TEST_SUITE_COMPLETION_MATCHER
+end
+
+Then(/^I should see a red failed test mark$/) do
+  run_output.should include(red("✗"))
+end
+
+Then(/^I should see a green passing test mark$/) do
+  run_output.should include(green("✓"))
+end
+
+Then(/^I should see a non-utf prefixed output$/) do
+  run_output.should start_with("    " + green("."))
+end
+
+Then(/^I should not see the name of the test group$/) do
+  run_output.should_not include("RACTupleSpec")
+end
+
+Then(/^I should see a red error message$/) do
+  run_output.should include(red("⌦ " + SAMPLE_PODS_ERROR.gsub('error: ', '')))
+end
+
+Then(/^I should see a red compilation error$/) do
+  run_output.should include(red("expected identifier"))
+end
+
+Then(/^I should see a failed line$/) do
+  run_output.should include("[[thread.lastMessage should] equal:thread.];")
+end
+
+Then(/^I should see a cyan cursor$/) do
+  run_output.should include(cyan("                                                          ^"))
+end
+
+Then(/^I should see the undefined symbold message$/) do
+  run_output.should include(red("⌦ Undefined symbols for architecture x86_64"))
+end
+
+Then(/^I should see the symbol and reference that caused failure$/) do
+  run_output.should include("_OBJC_CLASS_$_CABasicAnimation")
+  run_output.should include("objc-class-ref in ATZRadialProgressControl.o")
+end
+
+Then(/^I should see the name of a pending test$/) do
+  run_output.should =~ PENDING_TEST_NAME_MATCHER
+end
+
+Then(/^I should see the test time in yellow$/) do
+  run_output.should include("#{yellow("0.026")}")
+end
+
+Then(/^I should see the test time in red$/) do
+  run_output.should include("#{red("0.101")}")
+end
+
+Then(/^I should see text matching "(.*?)"$/) do |text|
+  run_output.lines.to_a.last.strip.should == text
+end