Gatling Beginner Tutorial | Update for Part 1 & 2 | Scala version, Maven Dependencies |

[@sourickpal8557]

Does gatling support to scala 3.5 now ?

[@RaghavPal]

Sourick
Gatling 3.5 is compiled against Scala 2.13, which means it does not support Scala 3.5 directly.

[@harmeetsingh7583]

In report , how do we get the TPS measured ? As report doesn't shows anything

[@RaghavPal]

Hi Harmeet, in reports, check the Details tab

[@harmeetsingh7583]

@@RaghavPal thanks raghav. But didn't find any term called TPS in the details tab as well.
If i am misunderstand any chart/graph , then please guide me for the same

[@khuloudalshammari626]

I made a project with a dummy ABI for the university, but I did not how tow make the user delete the comment or post .How can I do that?

[@RaghavPal]

Not much info on that

[@Kidszone0981]

Hi raghav as per your instruction i have set up the scala in my PC, but when i click on Run Engine getting error below:
Exception in thread "main" java.lang.ExceptionInInitializerError
at Engine$.(Engine.scala:7)
at Engine.main(Engine.scala)
Caused by: java.lang.NullPointerException: Cannot invoke "java.net.URL.toURI()" because the return value of "java.lang.ClassLoader.getResource(String)" is null
at IDEPathHelper$.(IDEPathHelper.scala:5)
Can you please help me on this

[@RaghavPal]

Here are some suggestions:
1. Scala Directory Configuration:
- The error message suggests that there's an issue with the `IDEPathHelper` class, which is related to Gatling's configuration.
- Make sure that your Scala directory is correctly configured as a "Test Sources Root" in your IntelliJ project. Here's how to do it:
- Right-click on the `scala` folder in your project structure.
- Select "Mark Directory as" and then choose "Test Sources Root."
- This ensures that Gatling recognizes the Scala code as part of the test sources.
- After making this change, try running the Gatling engine again.
2. Java SDK Version:
- Ensure that you're using a compatible Java SDK version.
- Sometimes, mismatched Java versions can cause initialization errors.
- Go to "File" > "Project Structure" > "Project Settings" > "Project" and check the "Project SDK." If it's set to an incompatible version (e.g., Java 9), change it to Java 8 (1.8).
- Re-run the Gatling engine after updating the SDK version.
3. Gatling and Scala Versions:
- Verify that you're using compatible versions of Gatling and Scala.
- Make sure you have the correct Gatling version installed.
- If you're using Maven, check your `pom.xml` for the Gatling plugin version.
- Update your Gatling version if necessary.
- Also, ensure that your Scala version aligns with Gatling's requirements.
4. Dependencies and Classpath:
- Check if all necessary dependencies are correctly added to your project.
- Ensure that Gatling's JAR files and Scala libraries are included in the classpath.
- If you're using Maven, verify your `pom.xml` for the correct dependencies.
5. Clean and Rebuild:
- Sometimes, cached files or outdated artifacts can cause issues.
- Try cleaning your project (Build > Clean Project) and rebuilding it.
- Then attempt to run the Gatling engine again.
6. Update Gatling and Plugins:
- Make sure you're using the latest version of Gatling.
- Update the Gatling Maven plugin (if applicable) to the latest version.
- Check the Gatling documentation for any specific instructions related to your setup.
Remember to follow these steps one by one, and hopefully, you'll be able to resolve the issue
--