[GH-ISSUE #4278] [feature]: pw.setSecret #1555

New issue

Open

opened 2026-03-16 20:49:45 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 20:49:45 +03:00

Owner

Originally created by @driskell on GitHub (Aug 19, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4278

Is there an existing issue for this?

I have searched the existing issues

Summary

A test should allow setting not just a variable in the environment but a non-synced secret also.

There is a use-case here for storing tokens after a login request for use in other requests. Ideally these would be stored in secrets and non-synced.

Why should this be worked on?

There are two types of variables, variables and secrets, and it's not clear how to set a secret (or that you can't) from the Test panel. This would speed up testing where requests need a separate login request that is not part of the builtin family of methods.

Originally created by @driskell on GitHub (Aug 19, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4278 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary A test should allow setting not just a variable in the environment but a non-synced secret also. There is a use-case here for storing tokens after a login request for use in other requests. Ideally these would be stored in secrets and non-synced. ### Why should this be worked on? There are two types of variables, variables and secrets, and it's not clear how to set a secret (or that you can't) from the Test panel. This would speed up testing where requests need a separate login request that is not part of the builtin family of methods.