Move tests for dyestring parse and reconstruct

It all seems to be working now, and should be considered stable.

Should parseColor really belong in the resource manager?

1 files changed, 0 insertions, 12 deletions

diff --git a/test/mp/future.js b/test/mp/future.js
index 735342e..abcdffe 100644
--- a/test/mp/future.js
+++ b/test/mp/future.js
@@ -33,10 +33,6 @@ function unshiftLoadImageBind(url, tests) {
     return tests;
 }
 
-function testDyeParse(expected, input, mp) {
-    assert.dyeDataEqual(mp.dye.parseDyeString(input), expected);
-}
-
 function testDye(err, dyed, dyeable, mp) {
     var input = dyeable.data;
     var expected = dyed.data;
@@ -48,14 +44,6 @@ function testDye(err, dyed, dyeable, mp) {
 suite.addBatch({
     "The manaportal dye": {
         topic: load("mp/dye", "mp/resource").expression("mp").document(),
-        "parseDyeString": {
-            "extracts the dye channel data from the dyestring": testDyeParse.bind(null, dyeData, dyeString)
-        },
-        "asDyeString": {
-            "reconstructs the dyestring from the dye channel data": function(mp) {
-                assert.equal(mp.dye.asDyeString(dyeData), dyeString);
-            }
-        },
         "dyeImage": {
             "with the big recolorable cake": unshiftLoadImageBind("test/data/bigcake.png", {
                 "to the big white cake dyed by TMWW": unshiftLoadImageBind("test/data/whitecake.png", {