dogmatiq / dogmatiq/testkit

Check whether dogma.go (logging file) is still necessary.

Open
#172 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1
Forks
1
Avg merge
2m
Merged PRs (30d)
1

Description

See the description in dogma.go for why this was added. The Test type has been simplified greatly since this was implemented, and TestingT now includes the Helper() method, so this file may no longer be necessary.

The ideal would be to get the testing frame to show the log source as the line where the caller invoked Test.Prepare() or Test.Expect().

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read dogma.go and its description first, then inspect the Test type, TestingT.Helper(), and the Test.Prepare() and Test.Expect() call paths. Determine whether dogma.go can be removed while preserving the intended testing-frame source location. Done means the file's necessity is resolved and the log source points to the caller where possible.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing-qa
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.