Re: [WebCryptoAPI-tests] Webcrypto encrypt and decrypt tests (#3110)

Jim,

I think I've addressed your issues.

1 the algorithm of the key and the algorithm of the function do not match
- added tests for this for AES. Did not do this for RSA because there is
only one RSA algorithm that does encrypt/decrypt. so there was nothing to
change it to.

2. algorithms which do not support the encrypt/decrypt operation
- have not addressed this. I'm still not clear on the purpose of this.
Wouldn't 1 above handle it, combined with tests that the key has the
encrypt usage? Algorithms that don't support encrypt/decrypt could not get
a key that did support that usage.

3. missing aad for the GCM algorithm
- added

4. Change of the input array after the function call has been made
- added

In addition, instead of using step_timeout for calling done, I keep an
array of all Promises being tested, and use Promise.all to call done when
they've all resolved.

Charlie


View on GitHub: https://github.com/w3c/web-platform-tests/pull/3110#issuecomment-224420872

Received on Tuesday, 7 June 2016 21:31:44 UTC