...
| Week | Task/Plan | Status |
|---|---|---|
| May 24 - May 28 | Initial Project Plan. | Done |
| May 31 - June 11 | Introduction to project. Download the code from the branch and get familiar with the code. Learn the key functionalities of Hyperledger Fabric. Structure the already existing tests in unit, integration, and functional. Bring all the existing tests to work. | |
| June 14 - June 25 | Integrate the existing tests into GitHub Actions Pipeline, which gets triggered by every PR and Push to the master branch. | |
| June 28 - July 2 | Wrap up all tasks prior to Eval 1 | |
| July 5 - July 9 | Review all existing tests, their organization, and integration into github actions pipeline. Eval 1 | |
| July 12 - July 23 | Extend the overall test coverage. Develop some key end-to-end tests | |
| July 26 - August 6 | ||
| August 9 - August 13 | ||
| August 16 - August 27 | Eval 2 | |
| August 30 - Sept 3 | ||
| Sept 6 - Sept 17 | ||
| Sept 20 - 24 | ||
| Sept 27 - Oct 1 | Eval 3 | |
| Oct 4 - Oct 15 | ||
| Oct 18 - Oct 29 | ||
| Nov 1 - Nov 5 | ||
| Nov 8 - Nov 12 | Eval 4 Final evaluation and presentation of project |
Tasks
| Github issues macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Explanation
Explanation of the project goes here.
...
Methodology followed is here.
| Github issues macro | ||||||||
|---|---|---|---|---|---|---|---|---|
|