Transaction Type 53: Close a Crowdsale Manually
Each application under test (AUT) must adhere to The Master Protocol / Mastercoin Complete Specification and pass the applicable tests listed in Major Items & Scenarios To Be Tested.
The tests for Close a Crowdsale Manually include:
- user is able to enter a valid value for:
- Property identifier
- valid input data is parsed and interpreted correctly, including all valid MSC Protocol transaction types in the blockchain that are supported by the AUT
- erroneous input data, including a corrupted blockchain, is detected as not valid and handled correctly
- correct Close a Crowdsale Manually transactions are generated from valid test input data
- runtime error conditions are detected and handled correctly (e.g. insufficient funds, application/network/OS failure)
- all edge cases are handled correctly
- correct, meaningful messages reflecting transaction success/status or failure are presented to the user
For each test sequence, start in a known state and return to a known state after the test is complete. Run the tests separately and also simultaneously. The simultaneous tests should be run by the same users/addresses in the same roles where possible, and also by different users/addresses.
Where appropriate, tests should be run using the end-user UI and using the API directly.
- U1: Create Close a Crowdsale Manually message(s) with valid values for:
- Property identifier
- U1: See that the Crowdsale is no longer active
- U2: See that the Crowdsale is no longer active
- U1: Attempt to create Close a Crowdsale Manually message(s):
- Property identifier = 0, 1, 2 or any non-existent id or a Property identifier owned by another address
- U1: See that the Crowdsale is still active
- U2: See that the Crowdsale is still active
The tester and developer should work together to write and run procedures that thoroughly test this functionality in the AUT.