This week I went through the AESIllustrated code and updated the team spreadsheet with a few methods I found. I didn't really justify between needed/unneeded methods, instead; I went through every method and calculated the cyclomatic complexity of each method I reviewed. This specific task didn't really take much time. However, I did find myself drifting into the code. This drastically increased the time it took me to evaluate methods.
Ola
Wednesday, September 28, 2016
Methods for Unit Testing
We have devised that we will be testing for the
following methods:
(Please edit and add your methods)
Matthew Smeraglia:
- Rijndael.Decrypt(byte[] input) (CC Level 2)
- Constants.GetNumberOfRoundsLookupTable() (CC Level 3)
- RijndaelDecryptionTransformFactory.Create() (CC Level 5)
- PaddingUtilities.ApplyPadding() (CC Level 6)
Ellen Ericson
-FiniteFieldMath.AntiLog(byte) (CC
Level 2)
-FiniteFieldMath.Multiply(byte, byte) (CC Level
4)
-FiniteFieldMath.CalculateG(byte) (CC Level 5)
-FiniteFieldMath.CalculateF(byte) (CC Level 11)
Ola McDaniel
-ByteUtilities.GetBytes(string) (CC lvl 2)
-Round.Inverse(State, int) (CC lvl 3)
-PaddingUtilities.RemovePadding(PaddingMode,
byte[]) (CC lvl 5)
-KeySchedule.Rekey(byte[], int)
Bryce Butler
-ByteMatrix.Xor(ByteMatrix) (CC lvl 2)
-Rijndael.Encrypt(byte) (CC lvl 4)
-RijndaelEncryptionTransformFactory.Create() (CC
lvl 5)
-ByteUtilities.ToPolynomial(byte) (CC lvl 7)
Sunday, September 25, 2016
Saturday, September 24, 2016
Project set up
Hi All! I have added the project to or perforce team directory. I have also added the unit test framework to the project and have added test files for each of us (designated by name). This way we can all have our own space for writing our tests.
I have also created a spreadsheet for our team to use for finding complexity and assigning methods (link here). We can each go through and add methods to the complexity pools i set up. Afterward, we can each claim 4 from each complexity to write. This way we will know who is working on what.
I have also created a spreadsheet for our team to use for finding complexity and assigning methods (link here). We can each go through and add methods to the complexity pools i set up. Afterward, we can each claim 4 from each complexity to write. This way we will know who is working on what.
Blog Created!
Welcome to the team blog for Team E (name to be determined soon)!
Our Team Members include:
Our Team Members include:
- Bryce Butler (Lead)
- Ola McDaniel
- Matthew Smeraglia
- Ellen Ericson
Subscribe to:
Comments (Atom)