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.

Sign up for GitHub

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

Jump to bottom

Testing folder #240

Closed
adrianfreed opened this issue Jul 26, 2014 · 1 comment
Closed

Testing folder #240

adrianfreed opened this issue Jul 26, 2014 · 1 comment
Assignees
@ilzxc

Comments

@adrianfreed
Copy link
Member

Please make a testing folder that doesn't go out with the release.

I have been posting patches that cause "o." to fail or crash into issues.
These are very valuable as regression test cases so they should be put into patches in that testing folder that can be run prior to final release.

Please collect from us any traces of patches we have that caused failures in that the past that have been fixed.
ilzxc added a commit that referenced this issue Jul 29, 2014
@ilzxc
Testing folder with a patch instantiating all odot externals - Issue #…
b6025d4 
…240 & Issue #196
@ilzxc
Copy link
Contributor

ilzxc commented Jul 29, 2014

Pull to see a folder named testing - please add your attempts at unit-testing Max externals, known bugs in the expression language, and any other things that fit the bill.

@ilzxc ilzxc closed this as completed Jul 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ilzxc ilzxc

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adrianfreed @ilzxc