4 ms·

Or use one of the CI providers that will test your stuff on macOS (alongside Windows, FreeBSD, ...). Possibly for free, if your stuff is open source. I use th

Or use one of the CI providers that will test your stuff on macOS (alongside Windows, FreeBSD, ...). Possibly for free, if your stuff is open source. I use that for Windows, which I don't personally use at all, and it finds bugs and problems all the time. I wish someone would provide free (!) CI for some rarer OSes and CPU architectures too, but I can dream.

viraptor 7y ago
You can't fully test things this way. Not enough to make a serious release anyway. You can easily pass all tests while not being able to even start the app. You need at least one person with the real hardware to do testing.
- saagarjha 7y ago
  This really depends on the tests you're running.
  - viraptor 7y ago
    True. But in context of: "tests in a CI environment which costs you less than a MacBook", I don't believe anyone would go to the level that avoids those issues. It would take a lot of work and resources to replicate a "real run in clean, real environment".
    - saagarjha 7y ago
      Again, this depends on the tests you’re running and how you’ve set up your CI environment.
faissaloo 7y ago
Unfortunately MacOS testing is usually extremely slow due to limited numbers of machines to run tests on.