| Author |
Message |
< Erlang patches mailing list ~ erlang-eunit: optionally run code coverage analysis during e |
| Guest |
 Posted: Thu May 27, 2010 9:01 pm |
 |
|
|
Guest
|
Hi,
This patch adds code coverage analysis support to the EUnit
additions for Emacs that I contributed last year.
erlang-eunit: Optionally run code coverage analysis during eunit tests
Add a number of features to the emacs mode which make it easier to
work with eunit test cases while keeping track of code coverage.
* C-cC-ec:
Compile the module under test for code coverage analysis, run tests
and show the results of the coverage analysis in a new buffer.
* C-c-C-ev:
Compile the current module for code coverage analysis.
* C-cC-ea:
Show the results of the coverage analysis in a new buffer.
Since Chris Bernard added some features recently [1] to
erlang-eunit.el and our changes overlap a bit, I chose to base my
changes on his branch. This was before his changes were merged
into 'pu'. I hope that's OK.
git fetch git://github.com/klajo/otp.git
emacs-eunit-with-cover-from-run-current-test
Cheers,
Klas
________________________________________________________________
erlang-patches (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-patches-unsubscribe@erlang.org
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu May 27, 2010 9:02 pm |
|
|
|
Guest
|
Hi,
This patch adds code coverage analysis support to the EUnit
additions for Emacs that I contributed last year.
erlang-eunit: Optionally run code coverage analysis during eunit tests
Add a number of features to the emacs mode which make it easier to
work with eunit test cases while keeping track of code coverage.
* C-cC-ec:
Compile the module under test for code coverage analysis, run tests
and show the results of the coverage analysis in a new buffer.
* C-c-C-ev:
Compile the current module for code coverage analysis.
* C-cC-ea:
Show the results of the coverage analysis in a new buffer.
Since Chris Bernard added some features recently [1] to
erlang-eunit.el and our changes overlap a bit, I chose to base my
changes on his branch. This was before his changes were merged
into 'pu'. I hope that's OK.
git fetch git://github.com/klajo/otp.git
emacs-eunit-with-cover-from-run-current-test
Cheers,
Klas
________________________________________________________________
erlang-patches (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-patches-unsubscribe@erlang.org
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Fri May 28, 2010 2:43 pm |
|
|
|
Guest
|
On Thu, May 27, 2010 at 11:01:20PM +0200, Klas Johansson wrote:
> Hi,
>
> This patch adds code coverage analysis support to the EUnit
> additions for Emacs that I contributed last year.
>
> erlang-eunit: Optionally run code coverage analysis during eunit tests
>
> Add a number of features to the emacs mode which make it easier to
> work with eunit test cases while keeping track of code coverage.
>
> * C-cC-ec:
> Compile the module under test for code coverage analysis, run tests
> and show the results of the coverage analysis in a new buffer.
>
> * C-c-C-ev:
> Compile the current module for code coverage analysis.
>
> * C-cC-ea:
> Show the results of the coverage analysis in a new buffer.
>
> Since Chris Bernard added some features recently [1] to
> erlang-eunit.el and our changes overlap a bit, I chose to base my
> changes on his branch. This was before his changes were merged
> into 'pu'. I hope that's OK.
>
> git fetch git://github.com/klajo/otp.git
> emacs-eunit-with-cover-from-run-current-test
That caused some headace. I think I made a succesful rebase
onto the current 'dev'. Next time, instead of branching
off 'dev' and merging from 'cb/emacs-eunit-run-current-test'
(the merge causes rebase difficulties), just branch off
'cb/emacs-eunit-run-current-test' in his repository and develop
on top of that branch. That branch does not exist in the
git://github.com/erlang/otp.git repository but it was
the parent commit to
9ac8fb78f4463a3a26b0c40c7f5f5aa90898f605
"Merge branch 'cb/emacs-eunit-run-current-test' into dev"
by Chris Bernard, in this case
e946a61a0a41c6592931d7cdfbb2dc618f582100
"Add Emacs EUnit utility feature: run current test function."
Or, in this case since 'cb/emacs-eunit-run-current-test' was
merged into 'dev', just branch off 'dev' and develop
from there. But I guess when you started,
'cb/emacs-eunit-run-current-test' was not merged into 'dev',
leaving you only the previous suggestion...
Nevertheless. Thank you! It will be included in 'pu',
but not today, it became too late...
>
>
> Cheers,
> Klas
>
> ________________________________________________________________
> erlang-patches (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:erlang-patches-unsubscribe@erlang.org
--
/ Raimo Niskanen, Erlang/OTP, Ericsson AB
________________________________________________________________
erlang-patches (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-patches-unsubscribe@erlang.org
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Fri May 28, 2010 2:43 pm |
|
|
|
Guest
|
On Thu, May 27, 2010 at 11:01:20PM +0200, Klas Johansson wrote:
> Hi,
>
> This patch adds code coverage analysis support to the EUnit
> additions for Emacs that I contributed last year.
>
> erlang-eunit: Optionally run code coverage analysis during eunit tests
>
> Add a number of features to the emacs mode which make it easier to
> work with eunit test cases while keeping track of code coverage.
>
> * C-cC-ec:
> Compile the module under test for code coverage analysis, run tests
> and show the results of the coverage analysis in a new buffer.
>
> * C-c-C-ev:
> Compile the current module for code coverage analysis.
>
> * C-cC-ea:
> Show the results of the coverage analysis in a new buffer.
>
> Since Chris Bernard added some features recently [1] to
> erlang-eunit.el and our changes overlap a bit, I chose to base my
> changes on his branch. This was before his changes were merged
> into 'pu'. I hope that's OK.
>
> git fetch git://github.com/klajo/otp.git
> emacs-eunit-with-cover-from-run-current-test
That caused some headace. I think I made a succesful rebase
onto the current 'dev'. Next time, instead of branching
off 'dev' and merging from 'cb/emacs-eunit-run-current-test'
(the merge causes rebase difficulties), just branch off
'cb/emacs-eunit-run-current-test' in his repository and develop
on top of that branch. That branch does not exist in the
git://github.com/erlang/otp.git repository but it was
the parent commit to
9ac8fb78f4463a3a26b0c40c7f5f5aa90898f605
"Merge branch 'cb/emacs-eunit-run-current-test' into dev"
by Chris Bernard, in this case
e946a61a0a41c6592931d7cdfbb2dc618f582100
"Add Emacs EUnit utility feature: run current test function."
Or, in this case since 'cb/emacs-eunit-run-current-test' was
merged into 'dev', just branch off 'dev' and develop
from there. But I guess when you started,
'cb/emacs-eunit-run-current-test' was not merged into 'dev',
leaving you only the previous suggestion...
Nevertheless. Thank you! It will be included in 'pu',
but not today, it became too late...
>
>
> Cheers,
> Klas
>
> ________________________________________________________________
> erlang-patches (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:erlang-patches-unsubscribe@erlang.org
--
/ Raimo Niskanen, Erlang/OTP, Ericsson AB
________________________________________________________________
erlang-patches (at) erlang.org mailing list.
See http://www.erlang.org/faq.html
To unsubscribe; mailto:erlang-patches-unsubscribe@erlang.org
Post received from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
