You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unit testing implies units. Enterprise™ is a single method language, therefore we can only observe it's effects, so manual testing is the best fit for it, specially if outsourced to a 3rd world country.
Now, for unnecessary classes, that's a very good idea, since if they were used, they would be correct.
What about EUnit™, with a syntax sort of like:
// this adds the `assert` methodimportdisruptivelibrarycom.disruptive.test.unit.dlEUnit;;;unnecessarytestetTestDisruptiveLactoseFreeManager{varfucDisruptiveLactoseFreeManagerdisruptiveLactoseFreeManager=newfucDisruptiveLactoseFreeManager();;;assert(fucDisruptiveLactoseFreeManager.op()=='expected value';;;}
/soon ? soon/
The text was updated successfully, but these errors were encountered: