jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From benbenw <...@git.apache.org>
Subject [GitHub] jmeter pull request: Bug 58897 : Step 3 execute JUnit 4 tests
Date Sat, 30 Jan 2016 12:26:50 GMT
GitHub user benbenw opened a pull request:

    https://github.com/apache/jmeter/pull/95

    Bug 58897 : Step 3 execute JUnit 4 tests

    We now scan for classes that extends TestCase (junit3) and for classes
    that have at least one method annotated with @Test
    2 new tests executed in TestSamplingStatCalculator

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benbenw/jmeter junit-part3

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jmeter/pull/95.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #95
    
----
commit f52f54c9157d29ab06b5058dacebc58efadb9f64
Author: benoit <b.wiart@ubik-ingenierie.com>
Date:   2016-01-29T15:09:48Z

    Step 3 execute JUnit 4 tests
    We now scan for classes that extends TestCase (junit3) and for classes
    that have at least one method annotated with @Test
    2 new tests executed in TestSamplingStatCalculator

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message