-
JEP Task
-
Resolution: Delivered
-
P4
-
None
1 Test Methodology
Functional Test for DHKEM is described in section 4.1 of RFC 9180: Hybrid Public Key Encryption.
2 Test Inventory (optional)
- Functional Test of DHKEM when a single KEM instance asked to produce keys repeatedly (Ex: > 1000 times)
- DHKEM key size as per RFC 9180 @https://www.rfc-editor.org/rfc/rfc9180#name-key-encapsulation-mechanism
- Tests to verify KEM encapsulation and decapsulation process to be thread safe as indicated in javadoc
- Interop Test when keys generated through other JDK providers, such as SunPKCS11
Existing Tests
No changes required as there are no modified APIs.
New Tests
New Tests will be written to satisfy the requirement described in Test Inventory.
Deprecated Tests
N/A
3 Test Configurations (optional)
N/A
- blocks
-
JDK-8301034 JEP 452: Key Encapsulation Mechanism API
- Closed
- clones
-
JDK-8198710 Test Plan for JEP NNN: <Feature description>
- New
1.
|
100% public API coverage | Resolved | Rajan Halade | ||
2.
|
80% block coverage for Java code | Resolved | Rajan Halade | ||
3.
|
100% specification change coverage | Resolved | Rajan Halade | ||
4.
|
99% test stability | Resolved | Rajan Halade | ||
5.
|
100% option combination coverage | Resolved | Rajan Halade | ||
6.
|
80% line coverage for native code | Closed | Rajan Halade | ||
7.
|
100% non-trivial method coverage | Resolved | Rajan Halade | ||
8.
|
Develop additional Tests for KEM implementation | Resolved | Sibabrata Sahoo (Inactive) |