Skip to content
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

need a way to inject a random name into things #12

Open
cdent opened this issue Jan 26, 2015 · 4 comments
Open

need a way to inject a random name into things #12

cdent opened this issue Jan 26, 2015 · 4 comments
Milestone

Comments

@cdent
Copy link
Owner

cdent commented Jan 26, 2015

One way to do this would be to have another replacement magic string, such as $UUID which gets a uuid.

However would this be the same uuid throughout all replacements on the current request, or a different one with each replacement. If the latter, how do we refer to the name again (for example in uri and in data)? Presumably in those cases the test writer should just make something up?

@cdent
Copy link
Owner Author

cdent commented Feb 2, 2015

Gonna wait for a pressing need on this one.

@cdent cdent added this to the later milestone Feb 13, 2015
@cdent
Copy link
Owner Author

cdent commented May 22, 2015

One way to do this is to use $ENVIRON, loaded with info from a fixture.

@kiminoa
Copy link

kiminoa commented Jun 10, 2015

Another related use case...

I'm using this workaround with $ENVIRON and the fixture writing stuff out to my env for the moment, but I'm still running into some non-ideal moments. In some cases I want to pass in a token value with the current time (we've got a "user-friendly" start_at token which expects a formatted date-time string), so current_time winds up being a misnomer with this workaround.

@cdent cdent mentioned this issue Jun 9, 2016
@cdent
Copy link
Owner Author

cdent commented Feb 14, 2018

Dare we consider shell expansions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants