clevermicro/amq-adapter-python
clevermicro/amq-adapter-python
14
0
Fork 0
Code Issues 22 Pull requests 4 Projects Releases Packages 1 Wiki Activity Actions

Implement unit test #47

Merged
stanislav.hejny merged 11 commits from unittest-coverage-85 into develop 2025-05-19 14:30:16 +00:00
Conversation 2 Commits 11 Files changed 29 +3269 -421
hurui200320 commented 2025-05-16 10:19:44 +00:00
Member
Copy link

This PR implements the unit test and ensures the coverage is above 85%, with help from cursor to generate most of the unit test.

This PR implements the unit test and ensures the coverage is above 85%, with help from cursor to generate most of the unit test.
feat \#16 - add unittest for backpressure_handler and logging_utils
Some checks failed
Unit test coverage / pytest (push) Failing after 3h11m10s
Details
bc98351493
test(General): write test for pydantic serializer, fixed serialization bug
Some checks failed
Unit test coverage / pytest (push) Failing after 3h11m8s
Details
45357c42a8
 
This commit write unit tests for pydantic serializer using cursor ai, and found an issue related to serialization. Originally, the code uses comma to concat string, but map and list also has comma inside. During the deserialization, split using comma will break map and list, leaving `{` with first kv pair for map, and `[` with first element with list. Instead of using concat with comma as separator, I use json to encode the object dict.
Partially finished the unit test for file handler
Some checks failed
Unit test coverage / pytest (push) Failing after 3h4m2s
Details
98fc52fc26
issue #16 - fix the pytest hanging after test main thread exits
Some checks failed
Unit test coverage / pytest (push) Failing after 1m4s
Details
53dce69e8f
test(General): fix existing unit tests for cleverthis service adapter
Some checks failed
Unit test coverage / pytest (push) Failing after 1m10s
Details
883ea3400f
 
Should bump coverage rate to 62%
test(General): implement unit test for data parser, rabbitmq client and other python files
Some checks failed
Unit test coverage / pytest (push) Failing after 1m7s
Details
aec53f5b34
 
This commit bump the coverage rate to 77%
test(General): finished unit test, coverage 88%
All checks were successful
Unit test coverage / pytest (push) Successful in 1m8s
Details
Unit test coverage / pytest (pull_request) Successful in 1m6s
Details
2e12d5ab57
 
ISSUES CLOSED: clevermicro/amq-adapter-python#16
requested reviews from abed.alrahman, stanislav.hejny 2025-05-16 10:20:03 +00:00
forgejo-actions commented 2025-05-16 10:20:52 +00:00
Copy link

Coverage is 88%

Coverage is 88%
feat #16 - update version so the code can be published as artifact
All checks were successful
Unit test coverage / pytest (push) Successful in 1m19s
Details
Unit test coverage / pytest (pull_request) Successful in 1m17s
Details
3e0f769837
forgejo-actions commented 2025-05-19 14:30:16 +00:00
Copy link

Coverage is 86%

Coverage is 86%
hurui200320 deleted branch unittest-coverage-85 2025-05-20 06:50:17 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
abed.alrahman
stanislav.hejny
Labels
Clear labels
  
Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.

  
Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
1 man-hours worth of work for an expert with no learning curve.

  
Points
13
13 man-hours worth of work for an expert with no learning curve.

  
Points
2
2 man-hours worth of work for an expert with no learning curve.

  
Points
21
21 man-hours worth of work for an expert with no learning curve.

  
Points
3
3 man-hours worth of work for an expert with no learning curve.

  
Points
34
34 man-hours worth of work for an expert with no learning curve.

  
Points
5
5 man-hours worth of work for an expert with no learning curve.

  
Points
55
55 man-hours worth of work for an expert with no learning curve.

  
Points
8
8 man-hours worth of work for an expert with no learning curve.

  
Points
88
88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
A ticket that represents the same content as an existing ticket.

  
State
In Progress
A ticket that is actively being developed.

  
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Bug
Something that doesnt work as intended.

  
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
An error or improvement needed in the documentation.

  
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
Some new functionality not present.

  
Type
Legendary
A type of Epic which will contain other Epics.

  
Type
Support
Someone needs help using the project.

  
Type
Task
A generic task that doesnt fit into the other type categories.

  
Type
Testing
Work exclusively focusing on fixing or expanding testing.

No labels
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
hurui200320
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#16 Ensure UnitTest coverage at least 85%
clevermicro/amq-adapter-python
Reference: clevermicro/amq-adapter-python#47
No description provided.
Delete branch "unittest-coverage-85"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?