Selenium on several machines was failing with Connection Refused errors. This turned out to be caused by IPv6 entries (for example, “::1 localhost”) which were added by a recent MacOS upgrade. Commenting out those entries seemed to fix the problem (or work around it, anyway).
Some people expressed a style preference, in rspec, for “pending” rather than an empty “it” block, to make it easy to search for pending tests. Excessive pending tests may be an anti-pattern. On the other hand, writing pending tests, at least temporarily, may be a good way to sketch out an area of functionality before it is implemented.
We have sometimes found that editing selenium tests (but not other ruby files) in IDEA is incredibly slow (as in, 30 second pauses). Two things to try are removing the gems directory from the project (in favor of just those gems which you need to be able to look at in IDEA), or at least removing the selenium gems. Another such example is that IDEA can be really slow editing the end of a long fixture file. This is probably IDEA 7.0.3 or 7.0.4.
One of the teams was trying to reopen the
Timeclass to make
to_datepublic. Another pivot noticed that there is no built in
Timeclass in ruby.
Timeclass that is public. The most interesting one is that there is a private
to_datethat is added to
Timeclass when you include Yaml.
- We are looking for one more unix system administrator preferably with scalability experience to help with our infrastructure. The job description is here. Well there are obvious benefits and then there is also free breakfast :)
There is a ruby meetup tonight at Outside In, at 7pm.
For load testing, Load Testing With Log Replay from igvita.com has a review of several common tools.