-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test algorithm perspective functionality #296
Comments
An idea of how a test check list could look like can be seen in #287 |
Will start testing the first three items, after a plan for testing is established. |
@CharlotteMagister and I have just developed a checklist according to which the algorithm plug-ins are tested. The checklist contains the following 4 points:
Due to the small size of the algorithm GUIs (maximum one dialog box with 2 pages) the checklist is much smaller than for the normal plugins (#287). We decided against testing the validity of the results of the algorithms, because the algorithms are provided by the crypto-provider Bouncycastle and we trust that they are correct. |
Some Algorithms do not open at all:
List to be continued |
I tested Asymmetric Block Ciphers \ RSA. I did not find any issues with it, but when clicking between the Asymmetric Block Ciphers and the Operations View the change in the text displayed in the Help box appears inconsistent. Sometimes the text vanishes and sometimes it appears again. |
I tested Message Authentication Codes \ HMac \ CBCmacSerpent. I did find some issues. When the user wants to specify a parameter and just adds " " (Spacebar) the field "finish" is green and the user can finish the configuration. The field expects a hexadecimal input, but when the user types for example the letter "G" two times in a row the Finish-Button can be clicked. |
I tested: Pseudo Random Number Generators \ SHA1PRNG Both working as intended. |
Tested Password-Based Ciphers \ PbeWithSHAAnd3_KeyTripleDES_CBC: Nothing happens when you try to click run button. Also tested Signatures \ MeRSA: You cant decrypt message, the key dissapears. |
Working: |
Closed with the release of v1.0.0 |
Test Algorithm-Perspective
TODO: while testing the first ones, develop a scheme for evaluation like in #287. Try to find a good trade-off to the effect of maximum efficiency (we only want to see if there are any systemic problems).
These UI paths were deemed representative and should be tested. Post results as comments in this issue for now to be sorted out later.
The text was updated successfully, but these errors were encountered: