Add unittests for mojo CDM and Decryptor |
|||||
Issue descriptionThis is to track adding unit tests for MojoCdm, MojoCdmService, MojoDecryptor and MojoDecryptorService. The test should cover common scenarios and connection errors. See https://codereview.chromium.org/2070753002 for an example to test MojoRenderer and MojoRendererService. See issue 622901 for the bug to add tests for mojo AudioDecoder. See issue 622897 for the bug to add tests for mojo VideoDecoder.
,
Aug 28 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 28 2017
Most of the EME browser tests are running with the MojoCdm (in addition to pepper). However, the AesDecryptorTests should also have a Mojo variant, so keeping this issue open.
,
Aug 28 2017
We only have a few test cases in MojoDecryptorTest and we should add more before we launch mojo CDM on desktop. As for AesDecryptorTests, it's a bit odd that we have to keep a mojo variant of it. We can discuss more on it.
,
Dec 8 2017
It looks like we only have a few tests covering MojoDecryptor, mostly on resource release. We should add more tests to help catch bugs and prevent regression.
,
Aug 3
xhwang@ is this still p1, it doesn't seem to be actively worked on?
,
Aug 3
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xhw...@chromium.org
, Aug 26 2016Labels: -Pri-3 M-55 Pri-2