Support for Blazemeter -report option

[VaishaliGulve]

Hello,

I see that we have an option to run distributed tests directly from DSL. Do we also have an option to send the report to Blazemeter report? Currently , the Taurus wrapper provides that and we use that feature extensively. Can you please provide support for this feature?

[rabelenda]

Really interesting feature, thank you for asking and proposing it!

What do you think of something like this?:

testPlan(
        threadGroup(2, 10,
            httpSampler("http://my.service")
        ),
        blazeMeterReportUploader()
    )

And that listener can be part of existing jmeter-java-dsl-blazemeter module.

Any particular fields you usually set with taurus blazemeter reports?
I guess you usually set the BM token. Do you set report names or other fields?

[VaishaliGulve]

Thank you! Yes, BM token, test name, project name, report name these are the main fields. Also, currently it can be used in any of the below scenarios - 1. Distributed test ( where the test is internal and only the report is sent to BM) 2. BM Cloud 3. BM On premise. I am not very sure which of these options are currently supported by DSL. Thank you again, this is awesome and I am going to be extensively using DSL in upcoming months to completely implement CI/CD

[rabelenda]

Hello,

I think I need more info about your listed scenarios (eg: how does each listed option look nowadays for you, what is the general architecture or services involved) to help you, if you need any help with that.

You can run JMeter DSL with JMeter cluster implemented by yourself (using existing JMeter distributed execution support) or with one of the different services the DSL already provides built in integration (currently: BlazeMeter, OctoPerf, Azure Load Testing). Here are more details.

I am glad you find the DSL useful and exciting and are willing to incorporate it.

Thank you for letting us know.

[VaishaliGulve]

When it comes to testing in BM cloud or on prem, we need to be able to set specific engines since we have dedicated IPs , any options for that? Also, specifying engine names is required to test on premise. 2. We need to be able to specify csv files to be uploaded to BM

[rabelenda]

This is great!

In fact is something we expected users to ask after they start playing further with existing BM engine.

Nowadays the BM engine does not provide options for that but we can easily add them. Both for specifying engines and to upload csv files.

Now that you have requested this, we will prioritize it higher in our backlog.

Stay tuned for upcoming releases :)

[rabelenda]

Do you think that something like this will be enough for the need you describe in this thread?:

testPlan(
    threadGroup(1, 1,
        httpSampler(SAMPLE_LABEL, "https://localhost")
    )
).runIn(new BlazeMeterEngine(System.getenv("BZ_TOKEN"))
    .location("my-location", 2) // location name, location weight
    .location(BlazeMeterEngine.Locations.GCP_US_EAST_1 , 1))

[rabelenda]

About asset files (CVS), we can consider automatic upload (no need to specify nothing in engine, it will automatically upload files used in csvDataSource) and optional explicit asset upload through new .asset(file) method

[VaishaliGulve]

that works, let me take a look at csvDataSource

testPlan(
threadGroup(1, 1,
httpSampler(SAMPLE_LABEL, "https://localhost/")
)
).runIn(new BlazeMeterEngine("projectName", "testName", System.getenv("BZ_TOKEN"))
.location("my-location", 2) // location name, location weight
.location(BlazeMeterLocations.GCP_US_EAST_1 , 1)
.report(“reportName”)
.files(“list of fileNames”, true/false) // true - splitcsv enable, false - splitcsv disable

[VaishaliGulve]

On the jmeter remote testing:

public void testPerformance() throws Exception {
TestPlanStats stats = testPlan(
threadGroup(200, Duration.ofMinutes(10),
httpSampler("http://my.service")
)
).runIn(new DistributedJmeterEngine("BMtestName","host1", "host2")) // test name can be project name, test name
.report("BMreportName") // the test should be created in specified BM project
assertThat(stats.overall().sampleTimePercentile99()).isLessThan(Duration.ofSeconds(5));
}

}

[rabelenda]

Hello, we have just released a new version of jmeter DSL which automatically uploads resources to blazemeter and allows to select location. Let me know what do you think.

Regards

[VaishaliGulve]

That’s nice , let me test it and get back to you

…

On Fri, May 26, 2023 at 2:24 PM rabelenda ***@***.***> wrote: Hello, we have just released a new version of jmeter DSL <https://github.com/abstracta/jmeter-java-dsl/releases/tag/v1.11> which automatically uploads resources to blazemeter and allows to select location. Let me know what do you think. Regards — Reply to this email directly, view it on GitHub <#185 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7Y3DHT6STRYBIHDISAHKA3XID7PTANCNFSM6AAAAAAYEFSB64> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[VaishaliGulve]

Hi @rabelenda , Sorry for the late response. I am unable to find the right version of dependency for jmeter-java-dsl-blazemeter, to successfully build my test. What is the version i need to use? I tried the user guide, seems like its down, unable to access it this time.
Thanks

[VaishaliGulve]

Here is the error msg: [ERROR] Failed to execute goal on project jmeter-java-dsl-sample: Could not resolve dependencies for project us.abstracta.jmeter:jmeter-java-dsl-sample:jar:0.1-SNAPSHOT: Failed to collect dependencies at us.abstracta.jmeter:jmeter-java-dsl-blazemeter:jar:1.13: Failed to read artifact descriptor for us.abstracta.jmeter:jmeter-java-dsl-blazemeter:jar:1.13: Could not transfer artifact us.abstracta.jmeter:jmeter-java-dsl-blazemeter:pom:1.13 from/to artifactory authentication failed for us/abstracta/jmeter/jmeter-java-dsl-blazemeter/1.13/jmeter-java-dsl-blazemeter-1.13.pom, status: 401 Unauthorized -> [Help 1]

[rabelenda]

Is the guide still down for you? I can access it https://abstracta.github.io/jmeter-java-dsl/guide/#blazemeter

[rabelenda]

The version 1.11 includes the new feature, but you can use 1.12 or 1.13 as well.

[rabelenda]

The error you are getting seems to be cause by some Artifactory instance that you have configured in your maven settings or some proxy in your company redirects to. It looks like authentication is failing with such artifactory instance. Does that make sense?