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

test: add pagination next key test in ContractHistory #72

Merged
merged 6 commits into from
Aug 17, 2023

Conversation

170210
Copy link

@170210 170210 commented Aug 15, 2023

Description

Add a test case to ContractHistory function which calls "with pagination next key", since we have not tested when setting pagination next key.

How has this been tested?

Unit tests

Checklist:

  • I followed the contributing guidelines and code of conduct.
  • I have added a relevant changelog to CHANGELOG.md
  • I have added tests to cover my changes.
  • I have updated the documentation accordingly.(not needed)
  • I have updated API documentation client/docs/swagger-ui/swagger.yaml(not needed)

Signed-off-by: 170210 <j170210@icloud.com>
@170210 170210 changed the title test: add next pagination key test in ContractHistory test: add pagination next key test in ContractHistory Aug 15, 2023
Signed-off-by: 170210 <j170210@icloud.com>
@170210 170210 marked this pull request as ready for review August 15, 2023 05:01
@170210 170210 self-assigned this Aug 15, 2023
Signed-off-by: 170210 <j170210@icloud.com>
@170210 170210 requested a review from Kynea0b August 16, 2023 02:18
Kynea0b
Kynea0b previously approved these changes Aug 16, 2023
da1suk8
da1suk8 previously approved these changes Aug 16, 2023
@da1suk8
Copy link
Member

da1suk8 commented Aug 16, 2023

In Description on this PR

Add a test case to ContractHistory function which calls "which pagination next key",

-> "with pagination next key" is correct ?

Signed-off-by: 170210 <j170210@icloud.com>
@170210 170210 dismissed stale reviews from da1suk8 and Kynea0b via fe382b4 August 16, 2023 06:09
Signed-off-by: 170210 <j170210@icloud.com>
@170210 170210 force-pushed the fixup/contractHistory_nextKey branch from 39cf1b1 to 09a2da2 Compare August 16, 2023 09:49
@170210 170210 marked this pull request as draft August 16, 2023 09:50
@170210 170210 force-pushed the fixup/contractHistory_nextKey branch 2 times, most recently from 154f090 to 2f9842b Compare August 16, 2023 10:07
@170210 170210 marked this pull request as ready for review August 16, 2023 10:08
@codecov
Copy link

codecov bot commented Aug 16, 2023

Codecov Report

Merging #72 (1bd3e56) into main (f800042) will decrease coverage by 0.04%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #72      +/-   ##
==========================================
- Coverage   62.32%   62.29%   -0.04%     
==========================================
  Files          80       80              
  Lines        9966     9966              
==========================================
- Hits         6211     6208       -3     
- Misses       3429     3431       +2     
- Partials      326      327       +1     

see 1 file with indirect coverage changes

@da1suk8 da1suk8 self-requested a review August 16, 2023 10:54
@170210 170210 requested a review from Kynea0b August 17, 2023 02:10
@170210 170210 merged commit 07aec27 into Finschia:main Aug 17, 2023
@170210 170210 deleted the fixup/contractHistory_nextKey branch August 17, 2023 09:10
@zemyblue zemyblue mentioned this pull request Oct 19, 2023
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 this pull request may close these issues.

3 participants