But since I long for a "more generic setup", the execution order of the
given Assertions limits my use case. (JMeter adds the Assertions from "top to
down".)
By this I could concentrate on the Assertions, and avoid forget adding a
second JSR223 Assertion.
For ex
](https://github.com/apache/jmeter/assets/54536760/af2ca0d2-f1ea-453b-bdec-4672f8206231)
When an Assertion is added to a specific Sampler, and it failes, the
PostProcessor does persist this error. The reason is, JMeter executes
PostProcessors before Assertions.
Since the existing execution
milamberspace merged PR #5813:
URL: https://github.com/apache/jmeter/pull/5813
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jmeter.ap
FSchumacher commented on PR #5813:
URL: https://github.com/apache/jmeter/pull/5813#issuecomment-1518624698
Looks good to me
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
milamberspace opened a new pull request, #5813:
URL: https://github.com/apache/jmeter/pull/5813
## Description
Change from Assert class to Assertions from jupiter
## Motivation and Context
Improve the code
## How Has This Been Tested?
./gradlew test
juribes commented on issue #5755:
URL: https://github.com/apache/jmeter/issues/5755#issuecomment-1372293097
Also reproducible in:
**Java Version:**
java version "1.8.0_351"
**OS Version**
Edition Windows 10 Pro
Version 21H2
Installed on 2020-11-19
OS
juribes commented on issue #5755:
URL: https://github.com/apache/jmeter/issues/5755#issuecomment-1372289558
[AssertionBug.jmx.txt](https://github.com/apache/jmeter/files/10352870/AssertionBug.jmx.txt)
Here is a JMX that reproduces the error. The extension was changed to upload
to GitHub
juribes opened a new issue, #5755:
URL: https://github.com/apache/jmeter/issues/5755
### Expected behavior
When I create an assertion in an HTTP sampler that has a redirection as a
response and I need to add an assertion to the sub-sample, when I select the
radio button "Sub-samples
mmben commented on issue #5734:
URL: https://github.com/apache/jmeter/issues/5734#issuecomment-1344407939
Hi Felix,
just wanted to check back and see, if the sample I provided helped in any
way.
Would be great, if you could hint about it.
Cheers!
--
This is an automated message f
ecked.
I understood the `ignore status` switch to be scoped to what is defined by
the Response-Assertion only without affecting other Assertions. What do you
think?
[Sample_5734.zip](https://github.com/apache/jmeter/files/10057894/Sample_5734.zip)
--
This is an automated message from
FSchumacher commented on issue #5734:
URL: https://github.com/apache/jmeter/issues/5734#issuecomment-1320918623
Can you post a minimal test plan, that exposes the described behaviour?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
FSchumacher commented on issue #5677:
URL: https://github.com/apache/jmeter/issues/5677#issuecomment-1320918498
Can you give more information on the used test plan? I suspect, that the
Response Assertion "Status code is 200" has the flag `Ignore status` set. The
doc for that element contain
FSchumacher commented on issue #5734:
URL: https://github.com/apache/jmeter/issues/5734#issuecomment-1320860996
I think, this is intended behaviour, as it allows the assertions to switch a
failing request to be OK. The most prominent example for this is the
ResponseAssertion, that has the
mmben opened a new issue, #5734:
URL: https://github.com/apache/jmeter/issues/5734
### Expected behavior
When adding more than one assertion under an HTTP Request, and one of the
assertions fails, the request should be marked as failed, independent of which
one of the assertions
vlsi merged PR #726:
URL: https://github.com/apache/jmeter/pull/726
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org
F
SampathKumarAmex opened a new pull request, #726:
URL: https://github.com/apache/jmeter/pull/726
## Description
Used JUnit 5 assertions in the test to keep it consistent with @Test
annotation (JUnit 5)
## Motivation and Context
Used JUnit 5 assertions in the test to keep it
Github user asfgit closed the pull request at:
https://github.com/apache/jmeter/pull/341
---
; jmeter/trunk/docs/images/screenshots/webtest/http-request1.png
> > jmeter/trunk/docs/images/screenshots/webtest/http-request2.png
> > jmeter/trunk/docs/images/screenshots/webtest/http_login.png
> > jmeter/trunk/docs/images/screenshots/webtest/threadgroup.png
> >
jmeter/trunk/docs/images/screenshots/webtest/threadgroup.png
> jmeter/trunk/docs/images/screenshots/webtest/threadgroup2.png
> jmeter/trunk/src/components/org/apache/jmeter/assertions/
> JSONPathAssertion.java
> jmeter/trunk/src/components/org/apache/jmeter/
Github user FSchumacher commented on the issue:
https://github.com/apache/jmeter/pull/341
Yes, but also to enable us to filter in view results tree on those meta
information. It could be something like a comment, a thread name or anything
else.
---
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/341
Hi @FSchumacher ,
Good idea.
Is this in relation with https://github.com/apache/jmeter/pull/313 ?
Thanks
---
Github user FSchumacher commented on the issue:
https://github.com/apache/jmeter/pull/341
I wonder, whether instead of or additionally to the new `setIgnore` method,
we should add and expose a `setMetadata(type, content)` method.
I believe it would be useful for example to:
* m
Hello,
When you have elements at different scopes:
- Pre and Post Processors are processed from OUTER to INNER scope
- while assertions are processed from INNER to OUTER scope
I don't see any regression risk
I propose we align it.
See:
https://bz.apache.org/bugzilla/show_bug.cgi?id=
Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/341
Hi @max3163 ,
0/ In order to justify the user case, can you illustrate your use case ?
1/ I think we should add a log in debug level when we ignore a SampleResult
2/ Could you also add eit
GitHub user max3163 opened a pull request:
https://github.com/apache/jmeter/pull/341
Test isIgnore after post processor and assertions
Actually, the new setIgnore() method allow to not send the sampleResut to
all listeners.
But you have to set the property in the sampler, you
Hello,
Any thoughts on this ?
1/ Is the requirement exotic or not ?
2/ Should we fix how assertions are processed compared to Pre/Post
Processors ? I think it would be cleaner and there is few risk to introduce
regression AFAIU
On Tue, Oct 24, 2017 at 9:29 PM, Philippe Mouawad <
p.moua...@u
that.
I can workaround that using a JSR223 Assertion to test that particular
Sampler.
But couldn't we handle that OOTB on Response Assertion or am I missing some
already existing way ?
I was thinking of a possible way to implement it by having a "Reset
Assertions" assertion wh
11 13:38:53 2016
>> New Revision: 1734555
>>
>> URL: http://svn.apache.org/viewvc?rev=1734555&view=rev
>> Log:
>> RSyntaxtTextArea not compatible with headless testing
>> Replace calls to constructors with getInstance
>> Bugzilla Id: 59165
>>
>
t;
> jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/BeanShellAssertionGui.java
>
> jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/XPathPanel.java
> jmeter/trunk/src/core/org/apache/jmeter/config/gui/RowDetailDialog.java
> jmeter/trunk/src/core/org
On 8 December 2015 at 22:14, wrote:
> Author: pmouawad
> Date: Tue Dec 8 22:14:01 2015
> New Revision: 1718724
>
> URL: http://svn.apache.org/viewvc?rev=1718724&view=rev
> Log:
> #resolve #46
>
> Modified:
>
> jmeter/trunk/src/components/org/apache/j
meter/trunk/src/components/org/apache/jmeter/assertions/gui/HTMLAssertionGui.java
>
>Modified:
>jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/HTMLAssertionGui.java
>URL:
>http://svn.apache.org/viewvc/jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/HT
On 15 November 2013 20:52, wrote:
> Author: pmouawad
> Date: Fri Nov 15 20:52:46 2013
> New Revision: 1542394
>
> URL: http://svn.apache.org/r1542394
> Log:
> Bug 55694 - Assertions and Extractors : Avoid NullPointerException when scope
> is variable and variable is miss
An alternative is to replace
return super.resolveEntity(publicId, systemId);
with
return null;
as that is what the super method is documented to always do.
The problem arises from a bug in
org.xml.sax.helpers.DefaultHandler#resolveEntity.
It implements EntityResolver (which throws IOE), bu
**rsyntaxtextarea/**RtfTransferable.java:41:
> warning: [deprecation] plainTextFlavor in java.awt.datatransfer.**DataFlavor
> has been deprecated
> [javac] DataFlavor.plainTextFlavor // deprecated
> [javac] ^
> [javac]
nt.pom
jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/BeanShellAssertionGui.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/GenericTestBeanCustomizer.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/TextAreaEditor.java
jmeter/trunk/src/core/org/ap
the caller, or the exception should be handled silently.
Anyway, I think we'll probably need to download the source and compile it.
>> The code could check if the jar is present, and if not, download and build.
>
> It's just occured to me - the Maven jar was not created by t
ould check if the jar is present, and if not, download and build.
It's just occured to me - the Maven jar was not created by the
project, so may not be trustworthy.
>>> - ask on legal discuss if this really is a problem or not
>>>
>>>>
>>>>
>>>>> Ple
e jar is present, and if not, download and build.
>> - ask on legal discuss if this really is a problem or not
>>
>>>
>>>
>>>> Please remove the download part for now.
>>>>
>>>>> Added:
>>>>>
>>>>
nents/org/apache/jmeter/assertions/gui/BeanShellAssertionGui.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/GenericTestBeanCustomizer.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/TextAreaEditor.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/WrapperEditor
gt;
>>>>
>>>> Unfortunately, I don't found a direct link to the jar on official
>>>> website. I think we can keep the download from Maven repo2 (it's not the
>>>> mvvrepository.com site, and don't show any Lgpl li
er/trunk/eclipse.classpath
jmeter/trunk/res/maven/**ApacheJMeter_parent.pom
jmeter/trunk/src/components/**org/apache/jmeter/assertions/**
gui/BeanShellAssertionGui.java
jmeter/trunk/src/core/org/**apache/jmeter/testbeans/gui/**
GenericTestBeanCustomizer.java
jmeter/trunk/src/core/org/**a
t;> Modified:
>>> jmeter/trunk/LICENSE
>>> jmeter/trunk/build.properties
>>> jmeter/trunk/build.xml
>>> jmeter/trunk/eclipse.classpath
>>> jmeter/trunk/res/maven/ApacheJMeter_parent.pom
>>>
>>> jmeter/trunk/src/co
/maven/ApacheJMeter_parent.pom
jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/BeanShellAssertionGui.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/GenericTestBeanCustomizer.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/TextAreaEditor.java
ease remove the download part for now.
>>>
>>> Added:
>>>> jmeter/trunk/src/core/org/**apache/jmeter/testbeans/gui/**textarea.properties
>>>> (with props)
>>>> Modified:
>>>> jmeter/trunk/LICENSE
>>>> jmeter/trunk/build.propertie
ents/org/apache/jmeter/assertions/gui/BeanShellAssertionGui.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/GenericTestBeanCustomizer.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/TextAreaEditor.java
jmeter/trunk/src/core/org/apache/jmeter/testbeans/gui/WrapperEditor.java
j
props)
Modified:
jmeter/trunk/LICENSE
jmeter/trunk/build.properties
jmeter/trunk/build.xml
jmeter/trunk/eclipse.classpath
jmeter/trunk/res/maven/ApacheJMeter_parent.pom
jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/BeanShellAssertionGui.java
jmeter/tru
jmeter/trunk/LICENSE
> jmeter/trunk/build.properties
> jmeter/trunk/build.xml
> jmeter/trunk/eclipse.classpath
> jmeter/trunk/res/maven/ApacheJMeter_parent.pom
>
> jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/BeanShellAssertionGui.java
&g
> > Log:
> > Add final to field
> > Add logger.isDebugEnabled
> >
> > Modified:
> >
> jmeter/trunk/src/components/org/apache/jmeter/assertions/XMLSchemaAssertion.java
> >
> > Modified:
> jmeter/trunk/src/components/org/apache/jmeter/assertions/X
ect to thread corruption
>
> Are you sure?
>
> > Modified:
> >
> jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/XPathPanel.java
> >
> > Modified:
> jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/XPathPanel.java
> > URL:
> http
> jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/XPathPanel.java
>
> Modified:
> jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/XPathPanel.java
> URL:
> http://svn.apache.org/viewvc/jmeter/trunk/src/components/org/apache/jmeter/assertions/gui/XPath
r/trunk/src/components/org/apache/jmeter/assertions/XMLSchemaAssertion.java
>
> Modified:
> jmeter/trunk/src/components/org/apache/jmeter/assertions/XMLSchemaAssertion.java
> URL:
> http://svn.apache.org/viewvc/jmeter/trunk/src/components/org/apache/jmeter/assertions/XMLSchemaAss
e displayed text to the new language
>> >
>> > Issue is due to the fact that on a french computer, default locale is
>> fr_FR , so as _en bundles are missing it stays in French. Would be the same
>> for all non english computers.
>> >
>> > Added:
&
/ Choose Language does not change all
> the displayed text to the new language
> >
> > Issue is due to the fact that on a french computer, default locale is
> fr_FR , so as _en bundles are missing it stays in French. Would be the same
> for all non english computers.
&
yed text to the new language
>
> Issue is due to the fact that on a french computer, default locale is fr_FR ,
> so as _en bundles are missing it stays in French. Would be the same for all
> non english computers.
>
> Added:
>
> jmeter/trunk/src/components/org/apache/j
54 matches
Mail list logo
