The go-test-teamcity from 2tvenom

Does not support subtests (available since Go 1.7)

https://blog.golang.org/subtests

Just an improvement request, I make heavy use and here's a snippet of my output:

##teamcity[testFinished timestamp='2018-12-08T20:05:32.338' name='Test_DB']
    --- PASS: Test_DB/memory (0.00s)
        --- SKIP: Test_DB/memory/ensures_that_ref_starts_with_refs/ (0.00s)
            ref_test.go:43: not implemented yet
        --- PASS: Test_DB/memory/various_read/write (0.00s)
            --- PASS: Test_DB/memory/various_read/write/returns_true_when_writing_a_ref_for_the_first_time (0.00s)
            --- PASS: Test_DB/memory/various_read/write/returns_false_if_hash_is_unchanged_in_store (0.00s)
            --- PASS: Test_DB/memory/various_read/write/returns_true_if_hash_is_changed_overwritten_in_store (0.00s)
            --- PASS: Test_DB/memory/various_read/write/retrieves_an_existing_object_if_already_in_store (0.00s)
            --- PASS: Test_DB/memory/various_read/write/returns_unknown_ref_error_for_non_existent_objects_in_store (0.00s)
            --- SKIP: Test_DB/memory/various_read/write/write_symbolic_fails_if_the_ref_name_is_not_all_caps (0.00s)
                ref_test.go:80: not implemented yet
            --- PASS: Test_DB/memory/various_read/write/write_symbolic_returns_true_if_the_symbolic_ref_was_created_or_changed (0.00s)
            --- PASS: Test_DB/memory/various_read/write/write_symbolic_returns_false_if_the_symbolic_ref_was_created_or_changed (0.00s)
            --- PASS: Test_DB/memory/various_read/write/retrive_symbolic_returns_symbolic_ref_correctly (0.00s)
            --- PASS: Test_DB/memory/various_read/write/retrive_symbolic_returns_error_on_non_existent_ref (0.00s)
        --- PASS: Test_DB/memory/listing_objects (0.00s)
    --- PASS: Test_DB/fs (0.03s)
        --- SKIP: Test_DB/fs/ensures_that_ref_starts_with_refs/ (0.00s)
            ref_test.go:43: not implemented yet
        --- PASS: Test_DB/fs/various_read/write (0.03s)
            --- PASS: Test_DB/fs/various_read/write/returns_true_when_writing_a_ref_for_the_first_time (0.00s)
            --- PASS: Test_DB/fs/various_read/write/returns_false_if_hash_is_unchanged_in_store (0.00s)
            --- PASS: Test_DB/fs/various_read/write/returns_true_if_hash_is_changed_overwritten_in_store (0.00s)
            --- PASS: Test_DB/fs/various_read/write/retrieves_an_existing_object_if_already_in_store (0.00s)
            --- PASS: Test_DB/fs/various_read/write/returns_unknown_ref_error_for_non_existent_objects_in_store (0.00s)
            --- SKIP: Test_DB/fs/various_read/write/write_symbolic_fails_if_the_ref_name_is_not_all_caps (0.00s)
                ref_test.go:80: not implemented yet
            --- PASS: Test_DB/fs/various_read/write/write_symbolic_returns_true_if_the_symbolic_ref_was_created_or_changed (0.00s)
            --- PASS: Test_DB/fs/various_read/write/write_symbolic_returns_false_if_the_symbolic_ref_was_created_or_changed (0.00s)
            --- PASS: Test_DB/fs/various_read/write/retrive_symbolic_returns_symbolic_ref_correctly (0.00s)
            --- PASS: Test_DB/fs/various_read/write/retrive_symbolic_returns_error_on_non_existent_ref (0.00s)
        --- PASS: Test_DB/fs/listing_objects (0.00s)
PASS
ok      github.com/retro-framework/go-retro/framework/ref       0.074s
testing: warning: no tests to run
PASS
ok      github.com/retro-framework/go-retro/framework/repo      0.043s [no tests to run]
FAIL    github.com/retro-framework/go-retro/framework/resolver [build failed]
##teamcity[testStarted timestamp='2018-12-08T20:05:32.354' name='Test_Storage']
##teamcity[testFinished timestamp='2018-12-08T20:05:32.354' name='Test_Storage']
PASS
ok      github.com/retro-framework/go-retro/framework/storage   0.038s
testing: warning: no tests to run
PASS
ok      github.com/retro-framework/go-retro/framework/storage/memory    0.058s [no tests to run]
make: *** [test-units] Error 2

Error messages can't exceed about a megabyte

TeamCity automatically splits log lines longer than about a megabyte. That means that our naive strategy of outputting all of the log messages for a test when it fails will not work. We need to take just the last n lines and put them into the failure message, or some other similar strategy.

Does not report the package / path, causes same name tests to be collapsed

I've moved from the older "gotest-to-teamcity" to this package, and I've noticed that the tests output in team city is less detailed in this package.

Old and desired output would have shown in team city tests tab like so:
OK | TestSanity (company/project/package/something/something2) | |

In this package, the tests tab is less informative:
OK (4 runs) | TestSanity | |

This causes team city to collapsed 4 different tests, from different packages/directories, as a single line.

Test coverage support

Could you add test coverage support?
Go test has -cover flag.
TeamCity has a set of coverage (CodeCoverage*) metrics you can send using service messages :https://www.jetbrains.com/help/teamcity/custom-chart.html

2tvenom / go-test-teamcity Goto Github PK

go-test-teamcity's People

Contributors

Stargazers

Watchers

Forkers

go-test-teamcity's Issues

Does not support subtests (available since Go 1.7)

Error messages can't exceed about a megabyte

Does not report the package / path, causes same name tests to be collapsed

Test coverage support

subtests (added in Go 1.7) are misparsed as panics

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent