material-components_materia.../MaterialComponentsUnitTests.podspec
Jeff Verkoeyen d0092f692a Testing by convention.
Summary:
Similar to Catalog by convention, Testing by convention allows us to generate a fully-working unit test suite using CocoaPods wildcards.

The testing convention is to place unit test source files in a `tests/unit` folder within each component.

A complete "component by convention" now looks like so:

    component/
      examples/
        SomeExample.m
      src/
        ...
      tests/
        unit/
          SomeTest.m

This convention makes it trivially easy to run all tests in our project & generate coverage information. Here are our coverage results:

{F439}

Resolves https://github.com/google/material-components-ios/issues/106.

Reviewers: cjcox, ajsecord, #mdc_ios_owners

Reviewed By: ajsecord, #mdc_ios_owners

Projects: #material_components_ios

Differential Revision: http://codereview.cc/D158
2016-03-01 12:35:19 -05:00

14 lines
656 B
Ruby

Pod::Spec.new do |s|
s.name = "MaterialComponentsUnitTests"
s.version = "0.2.1"
s.authors = { 'Apple platform engineering at Google' => 'appleplatforms@google.com' }
s.summary = "A collection of stand-alone production-ready UI libraries focused on design details."
s.homepage = "https://github.com/google/material-components-ios"
s.license = 'Apache 2.0'
s.source = { :git => "https://github.com/google/material-components-ios.git", :tag => s.version.to_s }
s.platform = :ios, '7.0'
s.requires_arc = true
s.source_files = 'components/*/tests/unit/*.{h,m,swift}'
s.framework = 'XCTest'
end