Question posted in Xcode
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level
2
Answers
Grey sign appears when test is run successfully and u can click on it to check the performance results in left bar
Xcode has four indicators for the result of a test.
Green Tick – The test passed
Red Cross – The test failed
Gray Cross – The test failed, but it was expected to
Xcode will show you this only if you already declared that a test was expected to fail using the
XCTExpectFailure
API.It’s Xcode way to tell you "hey this test failed but I’m not going to report it as a failure because you told me it was expected." This is useful to avoid blocking a build in CI if because when there’s an expected failure.
I would encourage you to use
XCTExpectFailure
parsimoniously. It’s useful to avoid being blocked by a test failure that is unrelated to your work, but you should always take the time to go back and fix the failure, don’t leave theXCTExpectFailure
call in your test suite for long.Gray Arrow – The test was skipped
Xcode will show this when a test was skipped using
XCTSkipIf
orXCTSkipUnless
.Similarly to an expected failure, you don’t need to do anything about this because either you or someone else in your team added the API call to skip the test, meaning the behavior is expected. It’s useful to skip tests if they depend on certain runtime capabilities that might not be available on the device or Simulator executing a test run.