mockforge version 0.3.2 generate k6 scripts which is not working and throws error Unexpected token

[srikr]

Description

I am seeing following error when running following mockforge command:

mockforge bench --spec billing_subscriptions_v1.json --target https://<any_server> --scenario constant --vus 50

Error:

time="2025-11-25T10:37:47+05:30" level=error msg="could not initialize 'bench-results/k6-script.js': could not load JS test 'file:///root/srikr/Tools/OpenAPISpec/bench-results/k6-script.js': file:///root/srikr/Too ls/OpenAPISpec/bench-results/k6-script.js: Line 6:12 Unexpected token . (and 19 more errors)" Error: k6 execution failed: k6 exited with status: exit status: 107

Steps to Reproduce

1. Use the attached OpenAPI Spec(billing_subscriptions_v1.json)
2. Install mockforge version 0.3.2 using command: cargo install mockforge-cli
3. Run the command: mockforge bench --spec billing_subscriptions_v1.json --target https://<any_server> --scenario constant --vus 50
4. This will throw above mentioned error

Expected Behavior

mockforge command should generate proper k6 javascript which should be able to run all type of openapi specs

Actual Behavior

Currently the problem seems like mockforge creates k6 javascript with variable names with dot that is not acceptable which is making k6 run failing

Version

v0.3.2

Rust Version

rustc 1.91.1 (ed61e7d7e 2025-11-07)

Operating System

Ubuntu 22.04

Additional Context

billing_subscriptions_v1.json

Checklist

• I have searched existing issues for duplicates
• I have included all relevant configuration files
• I have included complete error messages
• I am using the latest version of MockForge

[srikr]

Any workaround on this is also much appreciated as I have a requirement on WAAP which needs to be tested ASAP.

[srikr]

@rclanan can you please help me here to fix or give me a work around...

[rclanan]

Thank you for bringing this to my attention, I will take a look at it today. I think I actually already have this fixed in my newest changes but haven't published a new version yet. I will confirm.

[rclanan]

I have found the issue, created some test using the json you provided and verified that it will indeed work. Pushing up the fix now and will deploy to crates.io shortly. Will update once it's deployed.

[rclanan]

Published: mockforge-bench v0.3.3 to crates.io
What was fixed:
Fixed issue #79: k6 script generation now handles operation IDs with dots/hyphens
Added JavaScript identifier sanitization to prevent "Unexpected token ." errors
All operations are properly included in generated k6 scripts

[srikr]

Thanks @rclanan and appreciate for the quick response. I will test all my usecases and get back to you on 0.3.3 version

[rclanan]

Not a problem at all, I appreciate you trying out this tool. I have been using it on my own projects as well to try and iron out any bugs that I can find. Yes, please let me know if you run across anything else and I will get it address as soon as I can.

I really appreicate you opening a ticket for the issue, glad to see someone is trying it out and providing me feedback! Going to leave this open until you confirm it works for your usecases.

[srikr]

@rclanan I dont see 0.3.3 version in here: https://crates.io/crates/mockforge-cli/versions should I need to wait for sometime or if i run this command: cargo install mockforge-cli will I get your fixes?

[rclanan]

I published the mockforge bench first, so that would get updated. I have the rest of the crates publishing now, so yes, if you were using cargo install mockforge-cli, if you can just wait, the publishing for the rest of the crates is still in progress and the cli is the last one that gets published. I can update once they are all published. Crates.io rate limits you so I have to pause in between crates.

[rclanan]

✅ Fixed in v0.3.4

This issue has been resolved in mockforge v0.3.4. The problem was that operation IDs containing dots (like billing.subscriptions.v1 or plans.create) were being used directly as JavaScript variable names in the generated k6 script, which caused the "Unexpected token ." error.

What was fixed:

1. Added sanitization function: A new sanitize_js_identifier() function now converts operation IDs with invalid JavaScript characters (dots, hyphens, etc.) into valid identifiers:

   • "billing.subscriptions.v1" → "billing_subscriptions_v1"
   • "plans.create" → "plans_create"
   • "plans.update-pricing-schemes" → "plans_update_pricing_schemes"

2. Updated k6 script generation: The Handlebars template now uses sanitized names for JavaScript variable declarations while preserving the original operation IDs in comments and string literals for readability.

3. Added comprehensive test: An integration test using the actual billing_subscriptions_v1.json file from this issue verifies that:

   • All operations with dots/hyphens are properly sanitized
   • No invalid variable declarations are generated
   • The script can be successfully parsed by k6

How to get the fix:

cargo install mockforge-cli --version 0.3.4

Or if you're already using 0.3.4:

cargo install --force mockforge-cli

The fix is verified and all tests pass. Your command should now work correctly:

mockforge bench --spec billing_subscriptions_v1.json --target https://<any_server> --scenario constant --vus 50

Thanks for reporting this issue! 🎉

[srikr]

Thanks @rclanan for the fix, based on the above instruction I was able install to successfully install 0.3.4 version. when I run the above mockforge bench command I am seeing following error
`root@waapclient1:/srikr/Tools# mockforge --version
mockforge 0.3.4
root@waapclient1:/srikr/Tools# mockforge bench --spec

k6-script.js

billing_subscriptions_v1.json --target https://<server_ip> --scenario constant --vus 50
2025-12-01T01:49:48.202052Z INFO mockforge_observability::logging: Logging initialized: level=info, format=text

MockForge Bench - Load Testing Mode

────────────────────────────────────────────────────────────
Specification: /root/srikr/Tools/openapispec/paypal-rest-api-specifications/openapi/billing_subscriptions_v1.json
Target: https://192.168.2.86
Operations: 0 endpoints
Scenario: constant
Duration: 60s
────────────────────────────────────────────────────────────

→ Loading OpenAPI specification...
✓ Specification loaded
→ Extracting API operations...
✓ Found 16 operations
→ Generating request templates...
✓ Request templates generated
→ Generating k6 load test script...
✓ k6 script generated
✓ Script written to: bench-results/k6-script.js
→ Executing load test...
Starting load test...

⠁ Running load test...
time="2025-12-01T07:19:48+05:30" level=error msg="GoError: Invalid metric name: 'plans.list_latency'. Metric names must only include up to 128 ASCII letters, numbers, or underscores and start with a letter or an u
nderscore.\n\tat file:///root/srikr/Tools/bench-results/k6-script.js:6:28(24)\n" hint="script exception"
Error: k6 execution failed: k6 exited with status: exit status: 107`

Also attaching the k6 script which got generated seems like variable name is proper with underscores.. not sure why still its saying invalid metric name