Closed paulbellamy closed 1 year ago
great work, if possible can you paste the summary console output at end of run, i.e. the --- PASS: ..
lines, withVerboseOutput=false
, just wanted to see how long the execution times are for new NODEJS steps?
@sreuland My local runs (with --VerboseOutput=true
, then filtered) look like:
--- FAIL: TestDappDevelop (931.63s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_installs,_deploys_and_invokes_a_contract (268.69s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_installs,_deploys_and_invokes_a_contract#01 (63.03s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_installs,_deploys_and_invokes_a_contract#02 (92.23s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_installs,_deploys_and_invokes_a_contract#03 (70.79s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_deploys_and_invokes_a_contract (74.01s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_deploys_and_invokes_a_contract#01 (75.35s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_deploys_and_invokes_a_contract#02 (67.09s)
--- PASS: TestDappDevelop/DApp_developer_compiles,_deploys_and_invokes_a_contract#03 (160.73s)
--- FAIL: TestDappDevelop/DApp_developer_uses_config_states,_compiles,_deploys_and_invokes_contract_with_authorizations (59.70s)
(The cli tests fail due to a cli/quickstart version mismatch on my machine)
Seems like the first one is slower because it is downloading & compiling some rust.
Fixes #4
Note, This doesn't enable the last node.js tests recently added. As it's not really clear how that should map to the cli's concept of identities etc.
This refactors some of the go machinery to break up between the cli tool and the nodejs tool.
TODO