You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Learn from kepler-metal-ci's report analysis, I want to proposal an new approach for us to improve our test code coverage and fixing memory leaks.
For now, we have our test coverage in report by golang command as ... --cover and memory leak detection as go build -xxx, which both are plain text result.
so
if we make a python script, reading those report, and
for unit test code generation.
filter by unit test result
- if this package is not on ban list(for example, version package do not need to test?)
- if some package's test coverage lower than a threshold.
- we send files inside this package to openAI to generate test result.
- we recevie the test code generate by openAI
- we rerun the test coverage with test files, if it improve test coverage for the package.
- create a new PR.
for memory leak detection
for each PR, filter by memory leak result
- if the issue is on ban list(for example, string or big slice/array moved to heap)
- if a new memory leak happen
- send the specific leak to openAI to see if this can be fixed or not?
- if new memory leak been added or the memory leak can be fixed as AI's suggestion.
- leave comments in PR for double check/manual review.
The text was updated successfully, but these errors were encountered:
maybe, we can enable pprof in benchmark testing(after we have unit test and benchmark testing, here means golang language level) and we can analysis pprof result as well.
Learn from kepler-metal-ci's report analysis, I want to proposal an new approach for us to improve our test code coverage and fixing memory leaks.
For now, we have our test coverage in report by golang command as
... --cover
and memory leak detection asgo build -xxx
, which both are plain text result.so
if we make a python script, reading those report, and
for unit test code generation.
for memory leak detection
The text was updated successfully, but these errors were encountered: