
| Key: |
WTR-158
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Bret Pettichord
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Watir
Created: 04/Jun/07 01:31 PM
Updated: 24/Nov/08 02:03 PM
|
|
| Component/s: |
HTML Controls
|
| Affects Version/s: |
None
|
| Fix Version/s: |
Next
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
The inspect method for Ruby objects should provide information about the ruby object. For example, the inspect method for Watir objects should reveal the how and why that were used to create the object.
Currently we do not have inspect methods and therefore certain utilities use the to_s method, which provides information about the html element, not the ruby object itself (and they do so in a verbose way that can be hard to read in debugging contexts).
Inspect is used by debuggers, assertion/expectation engines (e.g. rspec) and the like.
|
|
Description
|
The inspect method for Ruby objects should provide information about the ruby object. For example, the inspect method for Watir objects should reveal the how and why that were used to create the object.
Currently we do not have inspect methods and therefore certain utilities use the to_s method, which provides information about the html element, not the ruby object itself (and they do so in a verbose way that can be hard to read in debugging contexts).
Inspect is used by debuggers, assertion/expectation engines (e.g. rspec) and the like. |
Show » |
|