Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lack of Testing / CI - Bug or Feature? #5

Open
veloper opened this issue Aug 27, 2018 · 1 comment
Open

Lack of Testing / CI - Bug or Feature? #5

veloper opened this issue Aug 27, 2018 · 1 comment

Comments

@veloper
Copy link

veloper commented Aug 27, 2018

/soon ? soon/

@joaomilho
Copy link
Owner

joaomilho commented Aug 28, 2018

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` method
import disruptive library com.disruptive.test.unit.dlEUnit;;;

unnecessary test etTestDisruptiveLactoseFreeManager {
  var fucDisruptiveLactoseFreeManager disruptiveLactoseFreeManager =  new fucDisruptiveLactoseFreeManager();;;
  assert(fucDisruptiveLactoseFreeManager.op() == 'expected value';;;
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants