Support synchronous testing of transactions

[tymat]

Support synchronous testing of transactions

[tymat]

See this for our rationale:

https://github.com/LeastAuthority/ethereum-analyses/blob/master/GasEcon.md#predictability

[tcoulter]

Hi @tymat. If I understand what you wrote correctly, this is already built in. Truffle uses Pudding under the hood, which makes ABI functions and sendTransaction() not call their callback until the transaction has been processed. The syntax is different than your example, but the effect is the same. Pudding uses promises to allow you to write the following:

val = "..." # some address
test = TestContract.at(TestContract.deployed_address)
test.setter(val, {from: caller}).then (tx) ->
  # This code block won't be executed until the transaction tx has been processed.
  # Note: The next line returns a promise.
  test.addr.call()
.then (addr) ->
  assert.isEqual(addr, val)

This should produce the effect you're looking for. Let me know if I misunderstood.

[tcoulter]

The function within Pudding that does exactly what you described is here: https://github.com/ConsenSys/ether-pudding/blob/master/src/pudding.coffee#L100

[tymat]

@tcoulter Thanks. That seems to work. Is there a way to set the timeout values?

[tcoulter]

Ya, that's a feature of mocha. There are three different scopes the timeouts can apply to. Consider this example:

contract "TestContract", (accounts) ->
  # Each test has a timeout of ten seconds.
  @timeout(10000) 

  before "do something before", (done) ->
    # This before() hook has a timeout of 15 seconds.
    @timeout(15000)

  it "should test something", (done) ->
    # This test has a timeout of 30 seconds.
    @timeout(30000)

  it "should do something else", (done) ->
    # This test only has a timeout of 10 seconds, based on the timeout above.