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
I just had an idea while looking at Java things.
In Java there's something called the Java Compatibility Kit. It's basically a massive amount of Java code that runs and just does nothing. At least it does nothing if the implementation of Java is correct! ;D
So it's a testing library, not for testing code adjacent to the tests' code, but for testing the language itself! (a particular implementation of it, that is (like an "engine"!))
I saw talk of testing cases mentioned here :>
I wonder if this would be something people want to do / help with! :>
Just writing a bunch of CAOS code (tests) which do nothing if the engine is correct and fail if not XD (or maybe they "return" true or false, like maybe create an agent with a particular classifier and then store info in the NAME variables like AlbianWarp does? we can have a mix of various levels of if and how much data is "returned" if returning data is supported :> )
And then we group them together and call them the CAOS Compatibility Kit! :D
And it's used to help test if engines are CAOS "Standards Compliant" XD
(Understanding there may be false positives but not false negatives. Ie, there might not be a test for everything, but if it fails a test that is there, then something's definitely wrong!)
The text was updated successfully, but these errors were encountered:
We could also separate things into three groups if we wanted :3
• CAOS itself (like doif, setv, mame, etc.)
• Inanimate Content (like the map, physics, sprites, etc.)
• Creatures Content (the actual creatures, brains, genetics, etc.)
Largely for two reasons:
Then CAOS-itself things could be very easily tested on a platform that supports running caos outside of a game without such content :3
OpenC2E and CaoticDreams don't implement the "Creatures Content" part here and probably won't for some time (at least not to the level of perfection that this would be testing for!), so it's probably good to separate that out ^^'
We could make tags for these levels if not already! :D
I just had an idea while looking at Java things.
In Java there's something called the Java Compatibility Kit. It's basically a massive amount of Java code that runs and just does nothing. At least it does nothing if the implementation of Java is correct! ;D
So it's a testing library, not for testing code adjacent to the tests' code, but for testing the language itself! (a particular implementation of it, that is (like an "engine"!))
I saw talk of testing cases mentioned here :>
I wonder if this would be something people want to do / help with! :>
Just writing a bunch of CAOS code (tests) which do nothing if the engine is correct and fail if not XD (or maybe they "return" true or false, like maybe create an agent with a particular classifier and then store info in the NAME variables like AlbianWarp does? we can have a mix of various levels of if and how much data is "returned" if returning data is supported :> )
And then we group them together and call them the CAOS Compatibility Kit! :D
And it's used to help test if engines are CAOS "Standards Compliant" XD
(Understanding there may be false positives but not false negatives. Ie, there might not be a test for everything, but if it fails a test that is there, then something's definitely wrong!)
The text was updated successfully, but these errors were encountered: