Dec 24, 2025
WebRAT: The "Ghost" in Your Hardware
Read the full report on -
CyberDudeBivash offers real-time cybersecurity news, threat intelligence, zero-day vulnerabilities, malware reports, and security tools.
Loading...
seen from Malaysia
seen from United States
seen from Netherlands
seen from Netherlands
seen from Maldives
seen from United States
seen from Philippines
seen from South Korea
seen from Germany
seen from China
seen from Maldives
seen from United States
seen from China
seen from Türkiye
seen from China
seen from United States
seen from China
seen from United States
seen from Canada
seen from United States
WebRAT: The "Ghost" in Your Hardware
Read the full report on -
CyberDudeBivash offers real-time cybersecurity news, threat intelligence, zero-day vulnerabilities, malware reports, and security tools.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
@webrat from here
That was probably the most compelling threat Kate had ever heard. “I’ll get it out!” She promised the other woman, kneeling down by her side to look at her thigh. “Oh! Cool, it doesn’t look like it’s that deep.” Her head darted around for a second. “Is that Times Square Elmo?!” As soon as Kate thought Jessica was distracted, she pulled the arrow out straight so it would do minimal damage. “No venom blasting!”
Webrat Steps extension (Be more DRY)
Recently when I was working with Cucumber and Webrat, I found default webrat definition very interesting. Even in some case I didn't even had to write a single step definition. But while proceeding I found that something is missing from webrat definition. So I decided to extend it. And come up with some methods defined as below. To use them just download this file and put it under features/step_definitions/ You can copy below code clipboard. Now you can use above listed methods easily and I assure you that if you use them properly you do not have to write a single step definition. Their uses can be found against USE in the downloaded file. "Use the Rails the way Rails is" Happy Boarding :)
Use Capybara on any HTML fragment or page
 I was upgrading [Gemcutter](http://github.com/rubygems/gemcutter) to Cucumber and Capybara 1.0 yesterday from Webrat (a change long overdue!), and I discovered a neat little class within Capybara that is worth sharing. Basically, since I was moving the app from Webrat, matchers like `assert_contain` and `assert_have_selector` are no longer available. Capybara's `Node` class has a great `Matchers` mixin with [tons of goodies](http://rdoc.info/gems/capybara/1.0.0/Capybara/Node/Matchers) that can be used like so, in RSpec: page.should have_content("This should be on the page") page.should have_selector("a[href='http://thoughtbot.com']") Great, but how does one use that in functional/controller tests? Enter `Capybara::Node::Simple`, which I found purely by chance when source diving. This class' [docs](http://rdoc.info/gems/capybara/1.0.0/Capybara/Node/Simple) proclaim its usefulness:
It is useful in that it does not require a session, an application or a driver, but can still use Capybara’s finders and matchers on any string that contains HTML
Bingo! Now, how to use in our test suite? We're still on Test::Unit for Gemcutter, so I had to do the following in `test/test_helper.rb`: class Test::Unit::TestCase def page Capybara::Node::Simple.new(@response.body) end end Now the Gemcutter test suite can do assertions like so: assert page.has_content?("Rails (3.0.9)") assert page.has_selector?("a[href='/gems/rails/versions/3.0.9']") The whole diff is [on GitHub](https://github.com/rubygems/gemcutter/commit/1a6a38c8d7515b7a00d4749fa1f3c638fb7e4a32) if you'd like to see all of the changes of moving our functional tests from Webrat to Capybara. [Gabe](http://thoughtbot.com/about/#gberkewilliams) also found out that there's also a shortcut in Capybara for creating a `Simple`: `Capybara.string`. The [docs](http://rdoc.info/gems/capybara/1.0.0/Capybara#string-class_method) for this show that it's basically sugar on top of the `Simple` initializer: node = Capybara.string <<-HTML
Home
Projects
HTML node.find('#projects').text # => 'Projects' I think this pattern is really useful not just for upgrading suites from Webrat, but really anywhere you have an HTML fragment or string that you'd like to use Capybara's matchers on.
Search for the best Integration testing
When you make a Rails application, there are some things unit and functional tests just can't test. Like if something actually works in practice, or if caching is working the way it should. If you don't test these, you can get run into a lot of problems, especially if that code is an application installed in multiple places. And it can be a pain to make sure code you add works as intended before a release (if could take you hours to test). So how do you get around this?
Well one way is using a service called Selenium RC, combined with Test::Unit style scripts. Selenium opens a browser, and runs a series of actions you define in your tests. And this can be quite handy for things like JS/AJAX forms. But what if you don't need that? The whole process of loading a browser just to test the login is working, or that a cache is removed when something is updated doesn't need the features of a browser. So what do you use? Well myself and my work colleagues recently started using an integration system called Webrat, and it's worked out really well. Combined with a custom test helper, which provides various custom methods, and alongside gems like shoulda and factory-girl, we have written a series of integration tests that are both small in size, and fastest to run (currently 5.5mins) compared to similar tests with Selenium or by testing this stuff by hand. And what's more, once you have the gems in place, it's a simple rake test:integration call to run them. No browser configuration or starting up the Selenium RC server. There is however Selenium built into the Webrat gem, so if you need to do JavaScript testing, it's not hard to. Writing tests using Webrat has made writing tests fun (not tiresome) and I look forward to writing more of them in the future. I even wrote a neat (in my opinion anyway) method_missing definition that allows a bunch of different method calls to create users with permissions, or to setup new items, and some neat application specific item creation methods. Our entire integration test setup is contained within the test/integration folder, so feel free to check it out, particularly the integration_test_helper.rb and caching_test.rb (which demonstrates most of the code). I'm interested to hear how others have approached the problem though. How do you test you caching? How do you test AJAX functionality? Post in the comments.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming