Clean up the algorithms suite.

[aljones15]

• create test to ensure suite runs with all suites.
  Features:

1. puts proofChain tests behind features.proofChain
2. puts domain & challenge tests behind features.authentication
3. exports the algorithms suite
4. adds test support for algorithms suite for all existing suites

[PatStLouis]

If we are hardcoding 'Verifier' here, shouldn't this be called describeVerifier?

[aljones15]

good catch here as the tests use both issuer and verifier this should be changed to implementation probably.

[aljones15]

this should have been fixed by an line comment.

[PatStLouis]

when you say "create test to ensure suite runs with all suites", can you explain a bit more what does this mean exactly and the purpose? I'm not sure I understand it Is it to make sure these test suites are compatible with all cryptosuites? There's a test described as "should issue all suites", is that referring to an implementation or the vc-generator issuer?

[aljones15]

when you say "create test to ensure suite runs with all suites", can you explain a bit more what does this mean exactly and the purpose? I'm not sure I understand it Is it to make sure these test suites are compatible with all cryptosuites? There's a test described as "should issue all suites", is that referring to an implementation or the vc-generator issuer?

https://github.com/w3c-ccg/data-integrity-test-suite-assertion/pull/127/files#diff-c881620c2d55af0c2c4e4faa1f54c53bf9a946370ec4a40a39de3402cbdac73e

There is an internal suite that runs all data integrity suites against the algorithms suite to ensure they run.