Both the Test.Ligo.BaseDAO.Proposal and Test.Ligo.BaseDAO.Management test modules contain some of the definition of the scenarios to run as well as the TestTree.
This however results in long compilation times that can get to be quite inconvenient, especially in case of small changes.
Note: some sub-modules already exist, e.g. Test.Ligo.BaseDAO.Proposal.Vote for an entrypoint, others might need to be created (possible for a behavior).
Additionally, we should consider renaming Test.Ligo.BaseDAO.Proposal.Proposal to Test.Ligo.BaseDAO.Proposal.Propose.
Acceptance criteria
Scenarios for both proposals and management logic are defined in different sub-modules (existing or new).
If there are no reason against it Test.Ligo.BaseDAO.Proposal.Proposal is renamed to Test.Ligo.BaseDAO.Proposal.Propose
Clarification and motivation
Both the
Test.Ligo.BaseDAO.ProposalandTest.Ligo.BaseDAO.Managementtest modules contain some of the definition of the scenarios to run as well as theTestTree.This however results in long compilation times that can get to be quite inconvenient, especially in case of small changes.
Note: some sub-modules already exist, e.g.
Test.Ligo.BaseDAO.Proposal.Votefor an entrypoint, others might need to be created (possible for a behavior).Additionally, we should consider renaming
Test.Ligo.BaseDAO.Proposal.ProposaltoTest.Ligo.BaseDAO.Proposal.Propose.Acceptance criteria
Test.Ligo.BaseDAO.Proposal.Proposalis renamed toTest.Ligo.BaseDAO.Proposal.Propose