forgejo

magic_rb/forgejo

Template

Fork 0

mirror of https://codeberg.org/forgejo/forgejo synced 2024-12-01 06:16:09 +01:00

Commit graph

Author	SHA1	Message	Date
KN4CK3R	f1173d6879	Use more specific test methods (#24265 ) Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: Giteabot <teabot@gitea.io>	2023-04-22 17:56:27 -04:00
wxiaoguang	911975059a	Improve test logger (#24235 ) Before, there was a `log/buffer.go`, but that design is not general, and it introduces a lot of irrelevant `Content() (string, error) ` and `return "", fmt.Errorf("not supported")` . And the old `log/buffer.go` is difficult to use, developers have to write a lot of `Contains` and `Sleep` code. The new `LogChecker` is designed to be a general approach to help to assert some messages appearing or not appearing in logs.	2023-04-21 16:32:25 -04:00

Author

SHA1

Message

Date

KN4CK3R

f1173d6879

Use more specific test methods (#24265 )

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Giteabot <teabot@gitea.io>

2023-04-22 17:56:27 -04:00

wxiaoguang

911975059a

Improve test logger (#24235 )

Before, there was a `log/buffer.go`, but that design is not general, and
it introduces a lot of irrelevant `Content() (string, error) ` and
`return "", fmt.Errorf("not supported")` .


And the old `log/buffer.go` is difficult to use, developers have to
write a lot of `Contains` and `Sleep` code.


The new `LogChecker` is designed to be a general approach to help to
assert some messages appearing or not appearing in logs.

2023-04-21 16:32:25 -04:00

2 commits