Jmeter error http test script recorder with Firestore Request

0
votes

I am testing a website that is using firestore.googleapis.com services, at some point I am blocked and I can't proceed to the test, due to this error from the firestore request:

Jmeter response data

Here's a copy of the request body:

Jmeter Request Body

I also did some troubleshooting with Firefox Developers Tools and I found this error on console:

Firefox Console Log

My configurations:

  • Jmeter Version: 5.4.1
  • Firefox Version: 85.0.2

Firefox is configured with Proxy so I can catch all the responses in the jmeter in port 8080 with HTTP test script recorder.

This just happens when I have the proxy configured in Firefox. If I turn the proxy off, the website works perfectly, already uninstall jmeter and remove certificates and add new ones, but the error appears always.

I have already tried Edge and Chrome with proxy configured, but with no success.

How can I "bypass" or fix this problem with firestore.googleapis.com/google.firestore.v1.Firestore?

1
firebasefirefoxgoogle-cloud-firestorejmeterperformance-testing
Please attach text instead of screenshot when it is possible. For example, you can put the request body and the error message as text in this post. It's hard to read it from the screenshot at this font size. – biqarboy

1 Answers

0
votes

Try clearing your Firefox browsing data, it might be the case Firebase connection is blocked by HSTS so your first visit to the website you're testing should be "clean".

Also if there is no essential data in the Firebase I would recommend skipping recording requests to it (as well as to other 3rd-party websites) as you load test should solely focus on your application. You can filter out the domains which shouldn't be in your test scope via "URL Patterns to Exclude" section of the HTTP(S) Test Script Recorder:

enter image description here

In the unlikely case of above hints don't help be aware of the alternative way of recording a JMeter test - JMeter Chrome Extension, it's not that "invasive" as JMeter so you shouldn't see any impact on your web application functionality.