Okay so yesterday I wrote a hypothetical blog post about a new testing framework that Apple made. I’ve got a lot of feedback – more than I expected, honestly. Developers really care about their tools.
One piece of criticism I received is that I hadn’t filed any bug reports with Apple asking for these features. I did include a link to Apple’s bug reporter and asked people to file radars, but I didn’t provide any radars to duplicate. That was an oversight on my part.
So here’s some due diligence: I have filed eleven radars with Apple asking for individual features that would each enhance the developer experience. They have all been cross-posted to Open Radar, so please feel free to duplicate them.
- 34875844 Xcode’s unit testing framework should include a mocking library
- 34875826 Hot Module Reloading
- 34875798 Open source Xcode, or make a new OSS Xcode Lite
- 34875762 Run unit tests in parallel processes/simulators
- 34875753 Xcode unit testing should support Behaviour-Driven Development workflows
- 34875723 Matchers that ship with Xcode’s testing framework could be improved
- 34875713 Xcode should schedule failing tests to run first
- 34873674 Xcode should only run tests related to files changed since the last commit
- 34873507 Add a test-on-save feature
- 34873492 Unit tests always run in the same order, but should be randomized
- 34876469 Isolate global state between tests by isolating tests
What features would make your day-to-day life as a developer easier, or more joyful?