-
Notifications
You must be signed in to change notification settings - Fork 18
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
writing a test code #1
Comments
if you have a test code, then the test can be automated on CI services, which is a common practice nowadays and can be done easily via tools like roswell |
Can you be more specific what you mean with this issue? Is this something not covered by https://github.com/pcostanza/mop-features ? (CLOS MOP issues are quite complex, so it's difficult to automate these tests...) |
Thanks, this seems what I have expected. I didn't noticed it because recently the test codes are usually in the same repository as the main implementation. by "automate" I mean Continuous Integration. Not only that it uses the latest Lisp impl, importantly anyone can see the output of the test code by each implementation on the browser. so it results in the less mental cost of using it. |
in short, my concern was how closer-mop is tested, and it turned out that I guess it is better if we add a reference of Even better is moving |
testing == unit testing, to be precise. |
Sorry for the late reply. It's difficult to have a test suite for Closer to MOP for several reasons. The specification for the MOP published in AMOP is ambiguous in some places and contradicts ANSI CL in others, so a consistent test suite is almost impossible. Also, the possibilities for implementing CLOS extensions using the MOP are pretty large, so it's hard to imagine how to be even remotely comprehensive. Secondly, the aim of MOP Features Tests is not to be a test suite for Closer to MOP. It's rather to test how close a particular CLOS implementation is already to the MOP specification. Closer to MOP is not an implementation of the MOP, but rather a set of fixes to bring existing MOP implementations closer to some understanding of the specification. In an ideal world, Closer to MOP should not be necessary. I hope this makes sense... Again, sorry for the late reply. |
I can work on it, but if you already have a set of testing code, I appreciate it very much
The text was updated successfully, but these errors were encountered: