"There are just four jobs remaining in the US. They are movies, music, microcode (software) and pizza delivery."
Well, so much for the government ability to develop complex software projects. I guess I will need to get a job from uncle Enzo.
The success in Ohio and Florida depends on the high voter turnout - if people stay home, because they think the race is over, Kerry could lose.
BTW Zogby is giving similar predictions, Kerry winning 311 eleven electoral votes.
http://www.zogby.com/
I go even further, and automate the integration test during the development phase. When the code is submitted, I update the general UI input/output routines and UI definintions, and have a working automated test.
Here are some lessons learned the had way in my 10+ years of automated testing experience:
1. Large scale automation is a very complex project. Think of it not as a testing activity, but as a full scale development project. Start with setting goals, then gather the requirements, and continue as you are writting product.
2. Get at least one person on the team which has participated in large test automation project. There are many common mistakes you can avoid.
3. Make an extensive analisys what you need to test. Some areas are very suitable for automation, others does not make it cost effective.
4. Always think of reducing the maintanance tasks. maintanance is the killer of the automated test. A good framework design will save you thousands of hours of work. One of the most commong approaches is to have separate interface components, so most changes in the UI will leave your tests unchanged.
5. Select the right tool for the job - there are hundreds of them on the market. Check the license price, the power of the scripting language, how it supports our interfaces, can it be integrated with other products. I especially like TestComplete, because is cheap and powerfull. But time for training is also an expences, and many companies select the most popular products there (from Mercury, Rational and Segue).
6. Participate in mailing lists, newsgroups, etc. It gives you the ability to get fast advise from some of the best people in this area.
And last, IMHO, the test automation, if done right, is always a winning strategy. But it is not a silver bullet.
Spirit and Opurtunity have only basic sampling capability (I think they can dig up to an inch or two). And Beagle 2, which had on board the "Mum" of MUM was lost.
Well, at least if Lucas and Spielberg reshoot "Raiders of the
Lost Ark" with the entire central cast replaced by ewoks, and destroy the original negative.
Slashdot Mirror
"There are just four jobs remaining in the US. They are movies, music, microcode (software) and pizza delivery." Well, so much for the government ability to develop complex software projects. I guess I will need to get a job from uncle Enzo.
The success in Ohio and Florida depends on the high voter turnout - if people stay home, because they think the race is over, Kerry could lose. BTW Zogby is giving similar predictions, Kerry winning 311 eleven electoral votes. http://www.zogby.com/
I go even further, and automate the integration test during the development phase. When the code is submitted, I update the general UI input/output routines and UI definintions, and have a working automated test.
Here are some lessons learned the had way in my 10+ years of automated testing experience: 1. Large scale automation is a very complex project. Think of it not as a testing activity, but as a full scale development project. Start with setting goals, then gather the requirements, and continue as you are writting product. 2. Get at least one person on the team which has participated in large test automation project. There are many common mistakes you can avoid. 3. Make an extensive analisys what you need to test. Some areas are very suitable for automation, others does not make it cost effective. 4. Always think of reducing the maintanance tasks. maintanance is the killer of the automated test. A good framework design will save you thousands of hours of work. One of the most commong approaches is to have separate interface components, so most changes in the UI will leave your tests unchanged. 5. Select the right tool for the job - there are hundreds of them on the market. Check the license price, the power of the scripting language, how it supports our interfaces, can it be integrated with other products. I especially like TestComplete, because is cheap and powerfull. But time for training is also an expences, and many companies select the most popular products there (from Mercury, Rational and Segue). 6. Participate in mailing lists, newsgroups, etc. It gives you the ability to get fast advise from some of the best people in this area. And last, IMHO, the test automation, if done right, is always a winning strategy. But it is not a silver bullet.
Spirit and Opurtunity have only basic sampling capability (I think they can dig up to an inch or two). And Beagle 2, which had on board the "Mum" of MUM was lost.
Useless trivia: The original Beagle drilling technology is is based upon a Hong Kong dentist's idea. The name of the guy is Dr. Ng.
And the guy with the sword will shoot first. Oh, the Humanity!
Well, at least if Lucas and Spielberg reshoot "Raiders of the Lost Ark" with the entire central cast replaced by ewoks, and destroy the original negative.
The payload and the range of SpaceShipOne is less then a primitive Scud rocket. It does not have military value.
LEO is Low Earth Orbit, so suborbital craft can never reach it.
Gravitation in LEO area is almost the same as here, on Earth.
Based on the name of the NIAC director (Robert Cassanova) I guess that one of the Sci-fi technologies is to how to get laid.