AuthenticJobs.com has branched out into the United Kingdom!
http://uk.authenticjobs.com
You get the same great interface but now in the United Kingdom as well.
AuthenticJobs.com has been around since 2005 and has been providing a great service for freelancers and companies looking for full-time, part-time and contract workers.
As of earlier today Sony announced that PSN – PlayStation Network would begin to be restored .
There is an update that Sony wants you to download which will require you to change your password.
It’s been 24 days since the outage began. Some suspect that the so called “hacker” group “Anonymous” was responsible but Anonymous claims the action to be rogue and that they are not involved.
Regardless of the direct or indirect involvement of Anonymous, I have to say that Sony’s response time clearly indicates a serious structural issue with their network and systems.
I think that JUnit’s description says it best, “Sometimes you want to temporarily disable a test.”
Here’s the whole thing for JUnit…
“Sometimes you want to temporarily disable a test. Methods annotated with Test that are also annotated with @Ignore will not be executed as tests. Native JUnit 4 test runners should report the number of ignored tests along with the number of tests that ran and the number of tests that failed.” - http://api.dpml.net/junit/4.2/org/junit/Ignore.html
And for Python these two links seem to begin to explain some of the thought behind the decisions to add this feature…
http://bugs.python.org/issue1399935
http://mail.python.org/pipermail/python-dev/2006-January/059503.html
I think this is one of those features that kind of got added on a slow day rather than really thinking about the impact that it has on the code and that reflection on the language. It makes sense right? You run your tests, you see some tests failing and you make a decision in your mind that you expected those to fail for a little while during development so you want them to stop sounding the alarm and blowing whistles!
This seems innocent enough at first but what are the long term implications?
Well firstly I think that you should really ask the question “Why do I have failing tests that I want to suppress??” I can’t think of any good reason personally. If you’re implementing something so huge that you’ve written tests that you can’t make pass before you test it on an integration server then you’ve probably bitten off more than you can chew and your feature will change/get removed before you can make the tests pass anyway.
Secondly, writing tests should be as simple as possible. Adding something extra to a testing framework, which also defeats the purpose of the framework, seems like we’re making things way more complicated than they have to be. A unittesting framework is supposed to tell you when things pass or fail. If you don’t want the tests to show up as failures and they do not indicate that something is broken then remove them.
Thirdly, maintenance…who’s going to clean this all up? You’ll see some places that warn the users of these features about this. Make sure that you remove this before you finally commit or merge to trunk! Why not just not worry about it by not using it?
If anyone has a really great use case for this please share in the comments! I may have my opinions/rants but I’m mutable 
Update:
This is an interesting perspective on the use of @expectedFailure. Basically it can allow you to manage bugs in third-party libraries. For instance if you find a new bug in some library that your’re using, you can write a test for that bug and when it gets fixed that will turn into an “unexpected success” and you can then clean up that test.
For me I still wonder how often this is truly useful. I haven’t seen a lot of tests written for bugs in third-party software. Also, if you have to use that part of the third-party library that has the bug then you must depend on that bug being there or not so you should have tests covering the outcome of the third-party’s bug.
The tests that you have will be covering “your” use of the third-party software. Obviously if the third-party software has a severe bug in it then you may decide not to continue using it.
Thanks Andrzej Krzywda! Great article on your blog.
So this is pretty big news eh!
LizaMoon is the domain that a newly discovered SQL injection vulnerability attempts to take viewers too. From there it will attempt to load FAKE anti-virus software onto your computer. It appears that this attack has affected nearly 1 million websites so far (http://www.google.com/search?q=%22src%3Dhttp:%2F%2F*%2Fur.php%22)
Websense.com has released excellent information and tracking of this SQL injection attack that appears to have start March 29th.
http://www.youtube.com/watch?v=wKI5dg1cs74
For more tracking of the injection attack visit WebSense.com’s community information at these urls…
Stackoverflow.com has an example and log information as well as some tips for server admins to attempt to clean and prevent the issue from happening again.
http://stackoverflow.com/questions/3788080/attack-on-asp-site-that-uses-a-sql-server-database
Also for system administrators, OWASP – The Open Web Application Security Project has excellent resources on how to manage the infamous SQL Injection risk.
http://www.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet
Since Sprint released an update for my HTC EVO 4g (3.70.651.1) my battery life has decreased significantly. The phone wouldn’t last much longer than 5 hours.
The battery life drained much faster in areas where I had poor service. This is normal in most cases but after the update the battery drain was much worse.
It appears that the in the update Sprint released for the HTC EVO 4g (3.70.651.1) increased some of the polling for the 3G data connection. So if I turn the wifi on and have it connect to access points instead of having it search for 3G then my battery lasts all day long and then some.
Tesla Motors used to have my affection and attention whenever they were in the news, but now they’ve decided to attack something else near and dear to me… Top Gear UK.
I’m sorry Tesla Motors, but you’re insane.
Jeremy Clarkson spent nearly the entire first half of their review praising the Tesla Roadster in the episode in question.
But as they do with all their reviews, they also pointed out some “consumer” issues with the vehicle they review. They do this with every single car they have on their show. And guess what! It’s entertaining!
Jeremy Clarkson, Richard Hammond and James May have dissed cars that cost several times as much as a Tesla Roadster.
Oh and so that we don’t forget how much we’re talking about here…The Tesla Roadster costs a staggering $101,500.
That’s including the $7500 government tax credit!
So I guess the ~2000 cars that Tesla has sold (That’s $203,000,000 btw) will all be returned due to this Top Gear turn down.
I guess what I’m trying to say is that if Tesla Motor’s sales are really being affected so much by a UK car show then maybe they should listen up and fix the problems that were noted by the Top Gear crew.
