Neotys loves great testers. But can you have high quality output without a dedicated Quality Assurance organization? That is the question posed and explored by Uri Nativ in this Slideshare. Uri claims that a dedicated QA function creates a wall between actions and consequences, making developers lazy.
This slideshare describes a process that includes a zero-bug policy and very short feedback loops to drive quality up. It recommends techniques like pair programming, TDD and BDD, dark launches and gradual rollouts. Apparently, if you put all this in place, you can avoid having to hire test engineers.
Do you buy it? Flip through the slides and decide for yourself.
A 17 year-old Londoner has pleaded guilty to a series of denial-of-service attacks against internet exchanges and the Spamhaus anti-spam service last year.
It’s pretty scary when you think about it. A teenager can muster the resources and expertise to bring down major online entities. According to reports, it’s unlikely that the teenager acted alone. Hackers used DNS reflection to amplify the DDoS attack. With peak traffic volumes exceeding 300 Gbps, this assault was one of the biggest DDoSes ever.
Are we that far from a time when a teenager could pull something like this off without much help? When an angry user with an axe to grind comes after any old website? Yours, perhaps? How well can you handle a spike in load from a DDoS attack?
Here’s the full story.
On October 28th and 29th, GTAC 2014, the eighth GTAC (Google Test Automation Conference), was held at the beautiful Google Kirkland office. The conference was completely packed with presenters and attendees from all over the world, bringing with them a huge diversity of experiences.
Speakers from numerous companies and universities (Adobe, American Express, Comcast, Dropbox, Facebook, FINRA, Google, HP, Medidata Solutions, Mozilla, Netflix, Orange, and University of Waterloo) spoke on a variety of interesting and cutting edge test automation topics.
Find pictures, slides, and video recordings from the recap here.
Help a fellow tester out with this question:
“I’m currently working on a folder synchronization tool which synchronizes the content of a specific folder with a remote cloud storage provider. In order to test the robustness of the client, I need a tool which generates random (but repeatable) file system operations (create file, modify file, delete file/folder, move file/folder, rename file/folder, etc.) in a way as similar as possible to the behavior of a real user.”
“The first idea that came to my mind was to create such a tool on my own. However, I’m wondering if I can find something that can make me save some time.”
Can you help? Contribute to the conversation.