If Mikrotik had a serious test suite for Router OS, they would not have been released such unusable crap software.
They need to write a serious test suite or they will be slower and slower at programming and debugging as soon as complexity will rise with IPv6 and Ethernet Provider new protocols.
Edit: I don't think it's necessarily crap, just very untested, and leaves users spending much unnecessary time testing.
I completely agree. It might be too late however, RouterOS is already extremely complicated with no test suite or consistency (change log problems, CLI inconsistency). I've been thinking of creating some kind of test suite from an external stance (auto config, auto enable/disable, auto monitor, etc...). If you have any ideas, I would love to get something together. Internally to Mikrotik source, we can't change that, there's nothing we can do there, but externally I think we could make something happen in regards to a test suite.
With webfig, swos, and hardware, the routeros platform (i believe) is being put on the back-burner with testing. This is a community supported software, yet me pay it to be closed source (not that I mind paying, I just wish us users were more involved with the software decisions and progress).