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

Access to Webrick log files for @akephalos scenarios #45

Open
ghost opened this issue Jan 20, 2011 · 2 comments
Open

Access to Webrick log files for @akephalos scenarios #45

ghost opened this issue Jan 20, 2011 · 2 comments

Comments

@ghost
Copy link

ghost commented Jan 20, 2011

I'm using Akephalos with Cucumber and Capybara. Some of my cucumber scenarios involve user authentication: these scenarios normally pass but when they're tagged @akephalos they fail -- the app responds with 401 Unauthorised and HTML Unit raises an error (com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException).

Here's the issue: it looks like Akephalos starts a separate Webrick server to handle @akephalos scenarios; where are the log files for this server? Is it possible to read the logs? I don't see anything in log/. Normally when a cucumber scenario is failing, my first step would be to check the logs, but in this case I'm stuck.

I'm using akephalos 0.2.4 (b2f056d), capybara 0.3.9, cucumber 0.10.0, cucumber-rails 0.3.2, and rails 3.0.1. I'm new to Akephalos so sorry if I've missed something obvious here :)

@mcmire
Copy link
Contributor

mcmire commented Feb 6, 2011

What happens if you tag the scenario @javascript @akephalos instead of just @akephalos? I got the same 401 error and this worked for me (although it may be specific to my setup).

@ghost
Copy link
Author

ghost commented Feb 7, 2011

Hey Elliot: did using the @javascript tag show logs for those scenarios like I described? That's the main issue, the 401 was just an example of the kind of situation where I wanted log access.

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

No branches or pull requests

1 participant