Skip to content
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

Run tests in geth and parity #171

Closed
izqui opened this issue Jan 8, 2018 · 12 comments
Closed

Run tests in geth and parity #171

izqui opened this issue Jan 8, 2018 · 12 comments
Milestone

Comments

@izqui
Copy link
Contributor

izqui commented Jan 8, 2018

Right now the test suite only runs on ganache-cli (former testrpc). Gearing up to mainnet deployment, we need to be running our tests in real nodes where code will eventually be deployed.

Great inspiration for how to do this right can be taken from the https://github.com/JoinColony/colonySale repo

@izqui izqui added this to the 0.5 code freeze milestone Jan 8, 2018
@status-open-bounty
Copy link

status-open-bounty commented Jan 8, 2018

Current balance: 0.0 ETH
Tokens: ANT: 20.00
Contract address: 0x5bddf0e51e487af3ccea6cb7070348424349008f
QR Code
Network: Mainnet
To claim this bounty sign up at https://openbounty.status.im and make sure to update your Ethereum address in My Payment Details so that the bounty is correctly allocated.
To fund it, send ETH or ERC20/ERC223 tokens to the contract address.

@izqui izqui changed the title Run tests in geth and/or parity Run tests in geth and parity Jan 8, 2018
@fgimenez
Copy link

hi @izqui! I'd like to give it a try. This is my very first issue, already set up on status.im, anything else needed to get started?

@izqui
Copy link
Contributor Author

izqui commented Jan 10, 2018

Sweet! Nothing needed to get started!

@fgimenez
Copy link

@cpurta you are doing a wonderful job on aragon/aragon-apps#66! I'm starting with this issue today but every question that has arisen for me so far is solved in your PR :) So please feel free to take this one too once you are done, I think that your current work could be adapted to this issue very nicely.

@trislit
Copy link

trislit commented Jan 25, 2018

Are you still looking at testing this? Are you attempting to test with payments through the front end api or just straight sendtocontract calls?

@nadavhollander
Copy link

@izqui Came across this across the interwebz because we're looking do the exact same thing at Dharma. Have you found any good leads on how to do this? I'm not sure how to recreate TestRPC functionality like evm_increaseTime in Geth / Parity

@sohkai
Copy link
Contributor

sohkai commented Jul 10, 2018

@nadavhollander That's a good question, I'm not sure if @cpurta has run into that issue with aragon/aragon-apps#66 yet...

There's an open spec that's under some discussion: ethereum/interfaces#4.

@cpurta
Copy link
Contributor

cpurta commented Jul 10, 2018

@nadavhollander I have ran into the same issue with Geth and Parity. They do not support that method in the RPC for good reason. Currently for testing you could not run any tests that make those calls when using those clients. I know that is a pretty bad solution to the problem but it may be better than the alternative.

The alternative would be making changes to one/both clients to support the method and maintaining a up to date branch with the master (or releases).

@sohkai
Copy link
Contributor

sohkai commented Jul 11, 2018

@nadavhollander Something to try (we kind of use this strategy) is avoiding use of any of the time utilities in ganache and using a mocked contract to set the time instead.

@aj07
Copy link

aj07 commented Jul 27, 2018

@izqui is this bounty still open for new contributors ? If yes, I would like to work on this

@sohkai
Copy link
Contributor

sohkai commented Aug 22, 2018

He @aj07; this has been put on standby for a while and @cpurta's done a really good job with #186 already.

@sohkai
Copy link
Contributor

sohkai commented Mar 18, 2020

Closing; as mentioned in #186, this is not a short term priority at the moment.

@sohkai sohkai closed this as completed Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants