-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write files #666
Comments
Unfortunately there's no way to write directly to the filesystem. That's mostly because of security and portability concerns when dealing with the distributed cluster and cloud execution. For easier debugging, we recently added a |
Thanks for the reply, I will look towards that for debugging. I guess I could also setup a collector server to record html/data as well. |
Yes, it would probably be easier for debugging more complicated scenarios. Another possibility is passing things through |
Closing this for now, since we don't currently plan to introduce support for writing files or other potentially unsafe operations. Logging with the |
Why not adding a --unsafe-operations flags in k6 for such cases ? Writing raw files can be useful eg: when you want them to be consumed by an existing process (which expects a specific format) Implementing a companion http server for that should work, but introduce extra overhead. Olivier |
@ofauchon, we now have xk6, so you can write unsafe extensions in Go that do pretty much anything, including write files. More details: It's a bit more involved, but at the same time it's much more flexible than what you suggest. It allows you to do anything, from writing files to apparently connecting to minecraft servers 😅 |
Hello, |
I am trying to determine why certain login tests are failing. To do so I need to examine the HTML that has been returned. While I realize that I can output this to the screen via console.log, it is cleaner and easier to read if it is output to a file. Is there anyway to write to the filesystem with k6?
Thanks
The text was updated successfully, but these errors were encountered: