Main Menu

script for automation test

Started by alt, June 18, 2014, 02:39:00 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

alt

Quote from: HackFisher on June 18, 2014, 05:43:40 AM
Quote from: alt on June 18, 2014, 05:41:33 AM
Quote from: HackFisher on June 18, 2014, 05:31:07 AM
+5%, alt!

Just a tip, there are already some testcase scaffolds under toolkit tests folder for regression tests. If anyone would like to help or describe the bug you found, jump to --->

https://github.com/BitShares/bitshares_toolkit/tree/master/tests/regression_tests

https://github.com/BitShares/bitshares_toolkit/tree/master/tests
thx, but I am confused, how to use this?

Here is the related document.
https://github.com/BitShares/bitshares_toolkit/blob/master/docs/regression_testing.dox
great, I'll learn to use this

HackFisher

Quote from: alt on June 18, 2014, 05:41:33 AM
Quote from: HackFisher on June 18, 2014, 05:31:07 AM
+5%, alt!

Just a tip, there are already some testcase scaffolds under toolkit tests folder for regression tests. If anyone would like to help or describe the bug you found, jump to --->

https://github.com/BitShares/bitshares_toolkit/tree/master/tests/regression_tests

https://github.com/BitShares/bitshares_toolkit/tree/master/tests
thx, but I am confused, how to use this?

Here is the related document.
https://github.com/BitShares/bitshares_toolkit/blob/master/docs/regression_testing.dox
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

alt

Quote from: CrazyBit on June 18, 2014, 04:31:19 AM
cool, it  could be used for stress test. but  i have no much fund.
test with other asset  :)
but still need some xts for the fee.

alt

Quote from: HackFisher on June 18, 2014, 05:31:07 AM
+5%, alt!

Just a tip, there are already some testcase scaffolds under toolkit tests folder for regression tests. If anyone would like to help or describe the bug you found, jump to --->

https://github.com/BitShares/bitshares_toolkit/tree/master/tests/regression_tests

https://github.com/BitShares/bitshares_toolkit/tree/master/tests
thx, but I am confused, how to use this?

HackFisher

 +5%, alt!

Just a tip, there are already some testcase scaffolds under toolkit tests folder for regression tests. If anyone would like to help or describe the bug you found, jump to --->

https://github.com/BitShares/bitshares_toolkit/tree/master/tests/regression_tests

https://github.com/BitShares/bitshares_toolkit/tree/master/tests
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

crazybit

cool, it  could be used for stress test. but  i have no much fund.

puppies

[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

alt


puppies

Are the missed transactions getting picked up over time?
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

alt

this is for flood test, 200 transfer everytime



#!/usr/bin/expect -f

set timeout -1

set wallet_name "default"
set account_from "alt"
set account_to "delegate-alt"
set loop_time 100
send_user "wallet name is: $wallet_name\n"
send_user "wallet passphrase: "
stty -echo
expect_user -re "(.*)\n"
stty echo
set wallet_pass $expect_out(1,string)

spawn ./bitshares_client --server --httpport 9989

expect -exact "--- there are now 1 active connections to the p2p network"
expect -exact "(wallet closed) >>> "
send -- "info\r"
expect -exact "(wallet closed) >>> "
send -- "wallet_open $wallet_name\r"
expect -exact "$wallet_name (locked) >>> "
send -- "wallet_unlock 999999\r"
expect -exact "passphrase: "
send -- "$wallet_pass\r"
#expect -exact "$wallet_name (unlocked) >>> "
#send -- "wallet_rescan_blockchain\r"
sleep 2

for {set i 1} {$i < $loop_time} {incr i 1} {
  expect -exact "$wallet_name (unlocked) >>> "
  send -- "wallet_transfer 10 DRINK $account_from $account_to \"test flood...\"\r"
  expect -exact "$wallet_name (unlocked) >>> "
  send -- "wallet_transfer 11 DRINK $account_from $account_to \"test flood...\"\r"
}

expect -exact "$wallet_name (unlocked) >>>
send -- "wallet_account_transaction_history\r"
interact

alt

I have write a  script to test toolkit automation
this can used to test some condition like flood transaction
I think somebody maye need this too

#!/usr/bin/expect -f

set timeout -1

set wallet_name "default"
set account_from "alt"
set account_to "delegate-alt"
send_user "wallet name is: $wallet_name\n"
send_user "wallet passphrase: "
stty -echo
expect_user -re "(.*)\n"
stty echo
set wallet_pass $expect_out(1,string)

spawn ./bitshares_client --server --httpport 9989

expect -exact "--- there are now 1 active connections to the p2p network"
expect -exact "(wallet closed) >>> "
send -- "info\r"
expect -exact "(wallet closed) >>> "
send -- "wallet_open $wallet_name\r"
expect -exact "$wallet_name (locked) >>> "
send -- "wallet_unlock 999999\r"
expect -exact "passphrase: "
send -- "$wallet_pass\r"
#expect -exact "$wallet_name (unlocked) >>> "
#send -- "wallet_rescan_blockchain\r"
sleep 2
expect -exact "$wallet_name (unlocked) >>> "
send -- "wallet_transfer 10 DRINK $account_from $account_to \"test flood...\"\r"
expect -exact "$wallet_name (unlocked) >>> "
send -- "wallet_transfer 11 DRINK $account_from $account_to \"test flood...\"\r"
expect -exact "$wallet_name (unlocked) >>> "
send -- "wallet_transfer 12 DRINK $account_from $account_to \"test flood...\"\r"
expect -exact "$wallet_name (unlocked) >>> "
send -- "wallet_transfer 13 DRINK $account_from $account_to \"test flood...\"\r"
expect -exact "$wallet_name (unlocked) >>> "
send -- "wallet_account_transaction_history\r"
interact
#expect -exact "$wallet_name (unlocked) >>> "
#send -- "exit\r"
#expect eof