Abstract
Develop automated testing framework for climate applications including the Fabric and Ethereum applications. Improve test coverage by writing additional tests. Integrate additional emissions calculators including the ThoughtWorks cloud carbon footprint calculator, the WRI GHG emissions spreadsheet, or the Allbirds emissions spreadsheet and add automated tests for them.
Mentor and Mentee
| Mentor | Mentor | Mentor | Mentee |
|---|---|---|---|
Si Chen US PST sichen@opensourcestrategies.com | Robin Klemens CEST r.klemens@yahoo.de | Kamlesh Nagware IST kamlesh.nagware@gmail.com | Pranamika Pandey IST pranamika.pihu1998@gmail.com |
Communication channel: Email + Discord + Github Tasks
Project repo: https://github.com/hyperledger-labs/blockchain-carbon-accounting/tree/mentorship-automated-testing
Deliverables
- 1 Structure tests into unit, integration, and functional. Get all existing tests to work.
- 2 Integrate tests into github actions pipeline to run on every push to the master branch.
- 3 Develop additional tests and end-to-end tests.
- 4 Implement some additional functionality, such as additional emissions data channels.
Milestones
Eval 1:
- a All existing tests are working and organized into unit, integration, and functional
- b Tests integrated into github actions pipeline.
Eval 2:
- c
- d
Eval 3:
- e.
- f.
Eval 4:
- g.
- h.
Timeline
| 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
Explanation
Explanation of the project goes here.
Methodology
Methodology followed is here.