https://github.com/ferd/trx

A rebar plugin to export Erlang test data into Visual Studio test format (.trx files)
https://github.com/ferd/trx

Last synced: 21 days ago
JSON representation

A rebar plugin to export Erlang test data into Visual Studio test format (.trx files)

• Host: GitHub
• URL: https://github.com/ferd/trx
• Owner: ferd
• License: apache-2.0
• Created: 2017-11-03T18:49:22.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2020-12-09T03:01:03.000Z (about 5 years ago)
• Last Synced: 2025-01-21T01:25:18.928Z (12 months ago)
• Language: Erlang
• Size: 21.5 KB
• Stars: 3
• Watchers: 3
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
trx

=====

A rebar plugin to export Erlang test data into Visual Studio test format (`.trx` files)

Use

---

Add the plugin to your rebar config:

    {project_plugins, [

        {trx, ".*", {git, "https://github.com/ferd/trx.git", {branch, "master"}}}

    ]}.

Then just call your plugin directly in an existing application to generate a report based on the latest common test run:

    $ rebar3 as test trx

    ===> Fetching trx

    ===> Compiling trx

    

Or do it automatically with a Common Test hook:

    {ct_opts, [{ct_hooks, [cth_trx]}]}.

These functions will generate a report under the right profile in the profile directory, under the latest Common Test name (like `ct_run.nonode@nohost.2017-11-03_14.40.29.trx`). To force a different name, declare the hook as:

    {ct_opts, [{ct_hooks, [{cth_trx, [{filename, "latest.trx"}]}]}]}.

And the file will instead bear that name (the path remains relative).

TODO

----

- Eunit integration

- PropEr integration (is it even possible?)

- Code coverage?