Skip to content

Instantly share code, notes, and snippets.

@dexX7
Created April 17, 2015 00:08
Show Gist options
  • Select an option

  • Save dexX7/1c126a507a64e23532a3 to your computer and use it in GitHub Desktop.

Select an option

Save dexX7/1c126a507a64e23532a3 to your computer and use it in GitHub Desktop.
:bitcoin-rpc:compileJava
:bitcoin-rpc:compileGroovy
:bitcoin-rpc:processResources UP-TO-DATE
:bitcoin-rpc:classes
:bitcoin-rpc:jar
:omnij-core:compileJava
:omnij-core:compileGroovy UP-TO-DATE
:omnij-core:processResources UP-TO-DATE
:omnij-core:classes
:omnij-core:jar
:omnij-rpc:compileJava
:omnij-rpc:compileGroovy
:omnij-rpc:processResources UP-TO-DATE
:omnij-rpc:classes
:omnij-rpc:compileIntegrationTestJava UP-TO-DATE
:omnij-rpc:compileIntegrationTestGroovy
:omnij-rpc:processIntegrationTestResources UP-TO-DATE
:omnij-rpc:integrationTestClasses
:omnij-rpc:regTest
foundation.omni.test.rpc.basic.SimpleSendSpec
    Can simple send 1.0 MSC from one address to another
    Can simple send 0.12345678 MSC from one address to another
    Can simple send 1E-8 MSC from one address to another
    When the amount to transfer is zero Simple Sends are rejected by the RPC
    When the amount to transfer is negative, Simple Sends are rejected by the RPC
    When the sending address has zero coins in its available balance for the specified currency identifier are rejected by the RPC
    When the amount to transfer exceeds the number owned and available by the sending address are rejected by the RPC
    When the specified currency identifier is non-existent are rejected by the RPC
foundation.omni.test.rpc.basic.ListPropertiesSpec
    Returns a property list with correct MSC and TMSC entries
foundation.omni.test.rpc.basic.ConsensusSpec
    Check all balances
    Check all balances, raw CLI, type Long
    Throw exception checking all balances, raw CLI, type String
foundation.omni.test.rpc.basic.SendRawTransactionSpec
    Create raw transaction with reference address
    Create raw transaction without reference address
foundation.omni.test.rpc.basic.OmniSpec
    Implement getbalance_MP
    Return Master Core version field using getinfo_MP
foundation.omni.test.rpc.dex.DexSpec
    A new sell offer can be created with Action = 1 (New)
    An accepted currency identifier for sell offers is CurrencyID:1
    An accepted currency identifier for sell offers is CurrencyID:2
    Offering more tokens than available puts up an offer with the available amount
    The amount offered for sale is reserved from the available balance
    Receiving tokens doesn't increase the offered amount of a published offer
    There can be only one active offer that accepts BTC
foundation.omni.test.rpc.misc.ClientConfigurationAndFundingSpec
    A newly generated address starts with 0.0 BTC, 0.0 MSC and 0.0 TMSC
    Requesting 1.0 BTC adds exactly that amount to the receivers BTC balance
    Requesting 0.00010000 BTC adds exactly that amount to the receivers BTC balance
    Requesting 0.00001000 BTC adds exactly that amount to the receivers BTC balance
    Requesting 1E-8 BTC adds exactly that amount to the receivers BTC balance
    The client accepts a transaction fee of 0.00010000 BTC
    Calculate dust amounts for common transaction output types
    The client accepts dust outputs with 0.00000546 BTC
    The client generates a "simple send" transaction with 2x 0.00000546 + 1x 0.00000684 BTC outputs
    Requesting 1.0 MSC adds exactly that amount to the receivers MSC balance
    Requesting 0.1 MSC adds exactly that amount to the receivers MSC balance
    Requesting 0.000001 MSC adds exactly that amount to the receivers MSC balance
    Requesting 1E-8 MSC adds exactly that amount to the receivers MSC balance
    Requesting 1E-8 MSC adds exactly that amount to the receivers MSC balance
foundation.omni.test.rpc.smartproperty.SmartPropertySpec
    Create smart property with divisible units
    Create test property with indisivible units
foundation.omni.test.rpc.exodus.MoneyManSpec
    Send BTC to an address to get MSC and TMSC
    check Spec setup
    Simple send MSC from one address to another
    Send MSC back to same adddress
foundation.omni.test.rpc.sto.SendToOwnersSpec
    STO calculates correct fees for the simple case
    STO fails when amount sent is zero
    The generated hex-encoded transaction matches a valid reference transaction
foundation.omni.test.rpc.sto.SendToOwnersTestPlanSpec
    Sender available balance = 0, reserved balance = 0 for the STO property
    Sender available balance = 0, reserved balance > 0 for the STO property
    Sender STO amount exceeds the number owned and available by the sending address, reserved balance > 0
    Sender does not have a sufficient MSC available balance to pay the transfer fee, MSC reserved balance > 0
    Sender MSC available balance = 0, MSC reserved balance > 0
    Sender owns all the coins of the STO Property after issuance (tx50, tx55) but before any distributions/sends
    Sender does not have sufficient MSC for STO amount + transfer fee
    One receiving owner (available balance > 0)
    Two equal owners (available balance > 0, amount divisible by number of owners)
    Three equal owners (available balance > 0,  amount divisible by number of owners)
    Two unequal owners (available balance > 0,  amount divisible by the proportion)
    Three unequal owners (available balance > 0,  amount divisible by the proportion)
    One receiving owner (reserved balance > 0)
    Two equal owners (reserved balance > 0, amount divisible by number of owners)
    Three equal owners (reserved balance > 0,  amount divisible by number of owners)
    Two unequal owners (reserved balance > 0,  amount divisible by the proportion)
    Three unequal owners (reserved balance > 0,  amount divisible by the proportion)
    One receiving owner (available balance > 0, reserved balance > 0)
    Two equal owners (available balance > 0, reserved balance > 0,  amount divisible by number of owners)
    Three equal owners (available balance > 0,  reserved balance > 0,  amount divisible by number of owners)
    Two unequal owners (available balance > 0, reserved balance > 0, amount divisible by the proportion)
    Three unequal owners (available balance > 0, reserved balance > 0, amount divisible by the proportion)
    Two equal owners (amount NOT divisible by number of owners)
    Three equal owners (amount NOT divisible by number of owners)
    Two unequal owners (amount NOT divisible by the proportion)
    Three unequal owners (amount NOT divisible by the proportion)
    Two equal owners (amount enough only for first owner)
    Three equal owners (amount enough only for first two owners)
    Two unequal owners (amount enough only for first owner)
    Three unequal owners (amount enough only for first two owners)
    Five equal owners (amount enough only for first four owners, amount NOT divisible by number of recipients)
    Five equal owners (amount enough only for first three owners, amount NOT divisible by number of recipients)
    Three unequal owners (amount enough only for first two owners, amount NOT divisible by proportion for recipients)
    STO Property ID is non-existent
    STO Property ID is 0 - bitcoin
    Sender owns all the coins of the STO Property, other addresses had non-zero balances but now zero balances
    Owners with similar effictive balances, but different available/reserved ratios, receive the same amount
foundation.omni.test.rpc.sto.SendToOwnersTestPlanRawSpec
    Sender available balance = 0, reserved balance = 0 for the STO property
    Sender available balance = 0, reserved balance > 0 for the STO property
    Sender STO amount exceeds the number owned and available by the sending address, reserved balance > 0
    Sender does not have a sufficient MSC available balance to pay the transfer fee, MSC reserved balance > 0
    Sender MSC available balance = 0, MSC reserved balance > 0
    Sender owns all the coins of the STO Property after issuance (tx50, tx55) but before any distributions/sends
    Sender does not have sufficient MSC for STO amount + transfer fee
    One receiving owner (available balance > 0)
    Two equal owners (available balance > 0, amount divisible by number of owners)
    Three equal owners (available balance > 0,  amount divisible by number of owners)
    Two unequal owners (available balance > 0,  amount divisible by the proportion)
    Three unequal owners (available balance > 0,  amount divisible by the proportion)
    One receiving owner (reserved balance > 0)
    Two equal owners (reserved balance > 0, amount divisible by number of owners)
    Three equal owners (reserved balance > 0,  amount divisible by number of owners)
    Two unequal owners (reserved balance > 0,  amount divisible by the proportion)
    Three unequal owners (reserved balance > 0,  amount divisible by the proportion)
    One receiving owner (available balance > 0, reserved balance > 0)
    Two equal owners (available balance > 0, reserved balance > 0,  amount divisible by number of owners)
    Three equal owners (available balance > 0,  reserved balance > 0,  amount divisible by number of owners)
    Two unequal owners (available balance > 0, reserved balance > 0, amount divisible by the proportion)
    Three unequal owners (available balance > 0, reserved balance > 0, amount divisible by the proportion)
    Two equal owners (amount NOT divisible by number of owners)
    Three equal owners (amount NOT divisible by number of owners)
    Two unequal owners (amount NOT divisible by the proportion)
    Three unequal owners (amount NOT divisible by the proportion)
    Two equal owners (amount enough only for first owner)
    Three equal owners (amount enough only for first two owners)
    Two unequal owners (amount enough only for first owner)
    Three unequal owners (amount enough only for first two owners)
    Five equal owners (amount enough only for first four owners, amount NOT divisible by number of recipients)
    Five equal owners (amount enough only for first three owners, amount NOT divisible by number of recipients)
    Three unequal owners (amount enough only for first two owners, amount NOT divisible by proportion for recipients)
    STO Property ID is non-existent
    STO Property ID is 0 - bitcoin
    Sender owns all the coins of the STO Property, other addresses had non-zero balances but now zero balances
    Owners with similar effictive balances, but different available/reserved ratios, receive the same amount
foundation.omni.test.rpc.sto.SendToManyOwnersSpec
    PropertyType:1: start with n * 1 and send n * 9223372036854775806 to 1 owners
    PropertyType:1: start with n * 9223372036854775806 and send n * 1 to 1 owners
    PropertyType:1: start with n * 1 and send n * 1 to 100 owners
    PropertyType:1: start with n * 1 and send n * 3 to 100 owners
    PropertyType:1: start with n * 1 and send n * 100000000 to 100 owners
    PropertyType:1: start with n * 100000000 and send n * 1 to 100 owners
    PropertyType:1: start with n * 100000000 and send n * 3 to 100 owners
    PropertyType:2: start with n * 1E-8 and send n * 92233720368.54775806 to 1 owners
    PropertyType:2: start with n * 92233720368.54775806 and send n * 1E-8 to 1 owners
    PropertyType:2: start with n * 1E-8 and send n * 1.00000000 to 100 owners
    PropertyType:2: start with n * 1E-8 and send n * 2.00000000 to 100 owners
    PropertyType:2: start with n * 1.00000000 and send n * 1E-8 to 100 owners
    PropertyType:2: start with n * 1.00000000 and send n * 2E-8 to 100 owners
    PropertyType:2: start with n * 1.00000000 and send n * 0.50000000 to 100 owners
    PropertyType:2: start with n * 1.00000000 and send n * 3.00000000 to 100 owners
foundation.omni.test.tx.OmniTxBuilderIntegSpec
    Can simple send amount MSC from one address to another using OmniTxBuilder and sendraw RPC

BUILD SUCCESSFUL

Total time: 2 mins 7.167 secs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment