summaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)AuthorFilesLines
2013-06-28Move tests for dyestring parse and reconstructFreeyorp2-15/+28
It all seems to be working now, and should be considered stable. Should parseColor really belong in the resource manager?
2013-06-28Extend assert for array and image assertionsFreeyorp3-23/+62
This also provides the much needed assert.arrayEqual
2013-06-28Add test for asDyeStringFreeyorp1-1/+6
2013-06-28Add test for the full colorspace of each channelFreeyorp3-8/+15
2013-06-26Implement dyeImageFreeyorp3-29/+46
Split loadImage into a common resource.js Add a compatability check for both canvas-node and browser functionality Note that the generated dyed image is off-by-one to the tested TMWW image. The algorithm needs verification and possibly correction. Either way, it's close enough by the eye.
2013-06-25Add dye API, canvas loading, future testsFreeyorp5-26/+107
The provisional API generates structured dye data from a dye string, and dyes an image when provided dyeable image data and the associated dyeing data. The splitting of an image URI and the dye string should probably be handled by a resource manager. Tests are distinguished between stable tests and future tests. Stable tests should pass at all times. Future tests should pass once implemented, and be moved to stable test suites. To run the future tests as well, run ./todo.sh. The current logic to load and extract image data should probably be refactored out from the test file and into some common file or resource manager file. Might need a custom assertion function for comparing image data to avoid flooding the console if something doesn't fully match. Finally, declare "use strict".
2013-06-25Add Jaxad's dye channel detectionFreeyorp2-0/+96
Set up tests