Skip to content

adding get method tests #185

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.

Sign up for GitHub

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

Merged
merged 12 commits into from
Jun 13, 2022
Merged

adding get method tests #185

Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
11ee0e0
adding get method tests
barnjamin Jun 7, 2022
e6a5e22
idk
barnjamin Jun 7, 2022
4c77318
Update features/unit/abijson.feature
barnjamin Jun 7, 2022
f21b592
adding extra test case for multiple same named methods
barnjamin Jun 8, 2022
e2036cb
Merge branch 'get-method-by-name' of github.com:algorand/algorand-sdk…
barnjamin Jun 8, 2022
126f53f
make error directive the same
barnjamin Jun 8, 2022
1651862
Update features/unit/abijson.feature
barnjamin Jun 9, 2022
9229c5a
Update features/unit/abijson.feature
barnjamin Jun 9, 2022
8c8fe85
update with correct verbiage
barnjamin Jun 9, 2022
827c506
Update features/unit/abijson.feature
barnjamin Jun 9, 2022
a46f2c7
adding tags
barnjamin Jun 13, 2022
11b4d6a
Merge branch 'get-method-by-name' of github.com:algorand/algorand-sdk…
barnjamin Jun 13, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 38 additions & 1 deletion features/unit/abijson.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
@unit.abijson
@unit
Feature: AbiJson

@unit.abijson
Scenario Outline: Serialize Method object from sig into json
When I create the Method object from method signature "<methodsig>"
And I serialize the Method object into json
Expand All @@ -16,6 +17,7 @@ Feature: AbiJson
| referenceTest(account,application,asset)uint8[3] | referenceTestMethod.json | abi_responsejsons |
| txnTest(txn,pay,keyreg,acfg,axfer,afrz,appl)bool | txnTestMethod.json | abi_responsejsons |

@unit.abijson
Scenario Outline: Create and serialize Method object into json
When I create the Method object with name "<name>" first argument type "<firstargtype>" second argument type "<secondargtype>" and return type "<returntype>"
And I serialize the Method object into json
Expand All @@ -26,6 +28,7 @@ Feature: AbiJson
| name | firstargtype | secondargtype | returntype | jsonfile | directory |
| add | uint32 | uint32 | uint32 | addMethod.json | abi_responsejsons |

@unit.abijson
Scenario Outline: Create and serialize Method object into json with arg names
When I create the Method object with name "<name>" first argument name "<firstargname>" first argument type "<firstargtype>" second argument name "<secondargname>" second argument type "<secondargtype>" and return type "<returntype>"
And I serialize the Method object into json
Expand All @@ -36,6 +39,7 @@ Feature: AbiJson
| name | firstargname | firstargtype | secondargname | secondargtype | returntype | jsonfile | directory |
| add | first | uint32 | second | uint32 | uint32 | addMethodWithArgNames.json | abi_responsejsons |

@unit.abijson
Scenario Outline: Create and serialize Method object into json with description
When I create the Method object with name "<name>" method description "<methoddesc>" first argument type "<firstargtype>" first argument description "<firstdesc>" second argument type "<secondargtype>" second argument description "<seconddesc>" and return type "<returntype>"
And I serialize the Method object into json
Expand All @@ -46,6 +50,7 @@ Feature: AbiJson
| name | methoddesc | firstargtype | firstdesc | secondargtype | seconddesc | returntype | jsonfile | directory |
| add | method description | uint32 | first description | uint16 | second description | uint32 | addMethodWithDescription.json | abi_responsejsons |

@unit.abijson
Scenario Outline: Check txn count of Method
When I create the Method object from method signature "<methodsig>"
Then the txn count should be <txncount>
Expand All @@ -55,6 +60,7 @@ Feature: AbiJson
| add(uint32,uint32)uint32 | 1 |
| txcalls(pay,bool,pay,axfer,byte)void | 4 |

@unit.abijson
Scenario Outline: Check method selector from Method
When I create the Method object from method signature "<methodsig>"
Then the method selector should be "<methodselector>"
Expand All @@ -63,6 +69,7 @@ Feature: AbiJson
| methodsig | methodselector |
| add(uint32,uint32)uint32 | 3e1e52bd |

@unit.abijson
Scenario Outline: Serialize Interface into json
When I create the Method object from method signature "<methodsig>"
And I create an Interface object from the Method object with name "<name>" and description "<description>"
Expand All @@ -74,6 +81,7 @@ Feature: AbiJson
| methodsig | name | description | jsonfile | directory |
| add(uint32,uint32)uint32 | ExampleInterface | This is an example interface | interface.json | abi_responsejsons |

@unit.abijson
Scenario Outline: Serialize Contract into json
When I create the Method object from method signature "<methodsig>"
And I create a Contract object from the Method object with name "<name>" and description "<description>"
Expand All @@ -86,3 +94,32 @@ Feature: AbiJson
Examples:
| methodsig | name | description | network1 | network1-app-id | network2 | network2-app-id | jsonfile | directory |
| add(uint32,uint32)uint32 | ExampleContract | This is an example contract | wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8= | 1234 | SGO1GKSzyE7IEPItTxCByw9x8FmnrCDexi9/cOUJOiI= | 5678 | contract.json | abi_responsejsons |


@unit.abijson.byname
Scenario Outline: Get a method by name from Interface
When I append to my Method objects list in the case of a non-empty signature "<methodsig>"
And I append to my Method objects list in the case of a non-empty signature "<extramethod>"
And I create an Interface object from my Method objects list
And I get the method from the Interface by name "<name>"
Then the produced method signature should equal "<methodsig>". If there is an error it begins with "<error>"

Examples:
| methodsig | extramethod | name | error |
| add(uint32,uint32)uint32 | | add | |
| add(uint32,uint32)uint32 | | sub | found 0 methods |
| add(uint32,uint32)uint32 | add(uint64,uint64)uint64 | add | found 2 methods |

@unit.abijson.byname
Scenario Outline: Get a method by name from Contract
When I append to my Method objects list in the case of a non-empty signature "<methodsig>"
And I append to my Method objects list in the case of a non-empty signature "<extramethod>"
And I create a Contract object from my Method objects list
And I get the method from the Contract by name "<name>"
Then the produced method signature should equal "<methodsig>". If there is an error it begins with "<error>"

Examples:
| methodsig | extramethod | name | error |
| add(uint32,uint32)uint32 | | add | |
| add(uint32,uint32)uint32 | | sub | found 0 methods |
| add(uint32,uint32)uint32 | add(uint64,uint64)uint64 | add | found 2 methods |