n1k0/casperjs — comment on commit f0b8a38ae09e8b30a3f807e86d6b9e04a8974755
File:  line 0
By srhyne:

Hi Nicolas,

No I haven't tried anything passed 0.4.2 since this is the tag the gh-page said was the stable version. I just checked out a "0.4.2.run_patch " branch and made my change there.

Is 0.4.2 still the most stable release?

Nicolas, you have done a tremendous job on this project! Way to go! It has more output polish that ghostbuster, a great testing lib like testling, it's headless, and has so many output options! I'm in love.

## Few questions..

### What would be the best way to add named arguments to cli array?

Example : --username srhyne --password *****

or ...

pass a JSON string as the second argument to run.js and then JSON.parse it into maybe casper.ARGS or something like that?

If you give me some direction on this I'll try to complete this feature and send a pull request.

## Evaluation scope?

So just to be clear... functions passed to the different Evaluate methods CANNOT share any scope with the casper suite correct ( besides the named arguments obj passed as the second argument)?

Perhaps I could enhance assertEval to pass in an arguments object?

## Wait

wait() works just like then, thenOpen right? You can just just do .wait(100).then(func) and that's the same as .wait(1000, func) right?

## Per test file best practice

I want to make sure my test files run in the desired sequence. What's the preferable way to manage the test file sequence?

Also, should I use casper.start in each test file even if the previous test file finishes on the url I am going to use for the next test file? (Does that make sense?)

# THANK YOU!