Skip to content

Conversation

@SomeRandomiOSDev
Copy link
Owner

A large number of the tests in this project are setup in a format like follows:

func testSomeRoutine() {
    testSomeRoutine(forType: Int8.self)
    testSomeRoutine(forType: Int16.self)
    ...
    testSomeRoutine(forType: UInt8.self)
    testSomeRoutine(forType: UInt16.self)
    ...
}

Prior to this change, assertions wouldn't notate which passed type caused the test failure. Now, using the new assertion functions CTAssertTrue, CTAssertFalse, CTAssertEqual propagates the name of the method that called it as well type it compares (for CTAssertEqual) for better visibility into the function, and more specifically, the type caused a particular test failure.

@codecov-io
Copy link

codecov-io commented Feb 21, 2020

Codecov Report

Merging #6 into 1.1.0 will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           1.1.0     #6     +/-   ##
======================================
  Coverage    100%   100%             
======================================
  Files          6      3      -3     
  Lines       1774    411   -1363     
======================================
- Hits        1774    411   -1363

@SomeRandomiOSDev SomeRandomiOSDev merged commit c5488b5 into 1.1.0 Feb 21, 2020
@SomeRandomiOSDev SomeRandomiOSDev deleted the 1.1.0_Testing branch February 21, 2020 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants