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

Add tests for DescribeWorkflowExecution in service/frontend/api/handler.go #6105

Conversation

fimanishi
Copy link
Member

What changed?
tests for DescribeWorkflowExecution in service/frontend/api/handler.go

Why?
improve unit test coverage

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

…er.go

**What changed?**
tests for DescribeWorkflowExecution in service/frontend/api/handler.go

**Why?**
improve unit test coverage

**How did you test it?**
unit tests

**Potential risks**

**Release notes**

**Documentation Changes**
Copy link

codecov bot commented Jun 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.20%. Comparing base (dc2a3a1) to head (7c6f2d3).
Report is 6 commits behind head on master.

Additional details and impacted files

see 14 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dc2a3a1...7c6f2d3. Read the comment docs.

@fimanishi fimanishi merged commit e09d945 into cadence-workflow:master Jun 5, 2024
20 checks passed
@fimanishi fimanishi deleted the tests-for-DescribeWorkflowExecution branch June 5, 2024 18:46
timl3136 pushed a commit to timl3136/cadence that referenced this pull request Jun 6, 2024
…er.go (cadence-workflow#6105)

**What changed?**
tests for DescribeWorkflowExecution in service/frontend/api/handler.go

**Why?**
improve unit test coverage

**How did you test it?**
unit tests

**Potential risks**

**Release notes**

**Documentation Changes**
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.

2 participants