Different response HTML being generated in integration tests
Reported by Rob Sterner | August 5th, 2008 @ 07:21 PM | in 2.x
I'll try to be as succinct yet informative as possible.
We've written some integration tests for our application that are asserting that the contents of a select > option drop down within an RJS response contain values that we expect. Each option > value is dynamically constructed (via links within our database), the only way to determine what the option > value should be is to generate it on the fly.
When running our test suite I'm seeing that 'rake test' results in the test passing as expected - the response rendered within the test case is what I'm expecting, something like:
(snippet)
In this case, we have an AR model representing a java class, SliceArrivalTime, whose calculated path is itinerary/slice/arrival@time. The path is *generated dynamically*, so it's as if our view file is, in one case, calling instance.path to render the response and calling instance.java_class.prettify (truncates com.foo.bar.Baz to Baz) in another.
This is the same test case using the same database being executed using a different task in the Rails rake task hierarchy. From everything I can poke at it looks as if the same controller/action/biz logic flow is being followed each time, the only difference is in what gets generated in the tests.
I know there probably isn't enough information here to get anyone started with debugging this, I'll be watching email and be in IRC (capndiesel) if anyone wants to chat about it.
Comments and changes to this ticket
-
Joshua Peek November 22nd, 2008 @ 07:49 PM
- → State changed from “new” to “wontfix”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
