-
Notifications
You must be signed in to change notification settings - Fork 93
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] 639 CFund Tests #640
Conversation
A new build of 1cb6165 has completed succesfully! |
A new build of 8af9dfa has completed succesfully! |
A new build of fb5d08d has completed succesfully! |
A new build of 87a744a has completed succesfully! |
IDK why the |
Ran all the tests and they all passed. |
What's the tl;dr on this PR?
…On Tue, Feb 25, 2020, 23:06 chasingkirkjufell ***@***.***> wrote:
Ran all the tests and they all passed.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#640?email_source=notifications&email_token=AAIDAKONWFK4YVABMSJNCTLREUXWLA5CNFSM4JQY5LYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM4JYNA#issuecomment-590912564>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIDAKIO636BS43NGFFY3WTREUXWLANCNFSM4JQY5LYA>
.
|
Functional testing of the cfund and potentially DAO. Things like creating a proposal and vote no and assert that the proposal is rejected. |
I've fixed this issue here: #715 |
@proletesseract if you have a few minutes, can you check out the conflict for I think this PR is ready to merge |
Conflicts: qa/rpc-tests/dao/test-plan.md
A new build of 37d6ca1 has completed succesfully! |
A new build of ededb0a has completed succesfully! |
Related to Issue #639
Adding the foundations for a comprehensive test suite for the NavCoin DAO / CFund.
I've removed the "Work in Progress" label on this PR. Instead of waiting for every test to be written i think its better to merge what is currently there and then slowly add tests otherwise we could be waiting forever until every possible scenario is covered.
It's important to understand that what is in this PR is just some simple building blocks, once the basics are covered we can use these building blocks to construct ever increasingly complex test scenarios and perhaps eventually even automate/randomise test scenarios to see if anything breaks after sequences of events which we might not think to test.
I've merged in the latest master and all the tests i've written so far are passing. Can I please get some reviews and comments or approvals.
The current test scenarios that are covered can be found in the test plan but are summarised below;
Scenarios
Scenario 001
./001-proposal-expired.py
Test Steps
Scenario 002
./002-proposal-rejected.py
no
votesTest Steps
no
on the proposalScenario 003
./003-proposal-accepted.py
yes
votesTest Steps
yes
on the proposalScenario 004
./004-proposal-expired-preq.py
Test Steps
Scenario 005
./005-proposal-expired-preq.py
Test Steps
no
on the proposalScenario 006
./006-proposal-accepted-preq.py
Test Steps
yes
on the proposal