On Monday, April 16th, NASA will launch TESS – Transiting Exoplanet Survey Satellite, which will search for nearby planets over the next 2 years. This is a follow on to the Kepler mission, and pre-cursor to the James Webb Space Telescope. What a time to be alive. You can follow the launch at NASA’s live site.
The TESS Spacecraft. Image Credit: NASA
One interesting tidbit, the TESS orbit is optimized to be able to observe the stars, and its not a near-Earth orbit. This means that the team needs to get it right, there won’t be an ability to fix the satellite after launch, like we did with Hubble. This means the team needs to get it right the first time.
MIT has produced a short (10 minutes) documentary about the making of TESS. This shows several interesting tidbits about testing:
TESS has 4 cameras, each with a test setup named after dragons. They used a simulated star field for each. For the cameras to operate correctly, each environment is in a vacuum chamber cooled down to -75C, and the ambient light is blue to minimize light pollution.
Testing the optics required the a team at the University of Geneva to invent “the most stable light source on earth”. (link) This light source had to be 10x more stable than the camera sensors.
Integration testing shows how the cameras are each mated to an assembly which holds all 4 cameras, then mounted to the main spacecraft.
The test team is predominately women, who are obviously passionate about this mission.
These videos, and the TESS program, are a great distraction from the other things happening in the news. We wish them luck.
After 32 years working for some of the top corporations, I’ve decided to go on my own. I’m my own boss.
Blessed in life, with a supportive family, and numerous people that I’ve worked with and admired, I’m going to try my hand at making a living by doing just my favorite parts of my job. These include:
- Coaching engineers and managers to help them become great leaders at the Software Leadership Academy
- Helping organizations apply Quality Engineering practices
- Transform test organizations into Quality Engineering Organizations
- Bring customer focus into the software development life-cycle with Customer-Driven Quality
- Accelerate testing by reducing or eliminating long regression cycles and moving to a continuous delivery model
- Help investors understand the developer productivity and testing tool/service marketplace.
I’ll be sharing more about my plans in the coming weeks, including a product launch for the online leadership course. You can watch progress at http://www.swleadership.com
Wish me luck!
Winter has come, and Game of Thrones fans enjoyed the first episode of season 7. This episode had a couple of good leadership lessons. By the old gods and the new, there are spoilers ahead, so read at your caution.
Jon Snow leading the North in Winterfell
Jon Snow is an inclusive leader, which will expand his influence. He embraced the wildlings earlier in the show and most recently the next generation of the Umbers and Karstarks. These moves build his collation, expand his influence, and will aid in the battle with the white walkers.
Most organizations have an “enemy” to help focus their strategy. The most successful organizations focus their efforts outside, towards beating a competitor or changing the status quo in the marketplace. I’ve seen places that concentrate, instead, on infighting between departments. These places don’t exist anymore.
Jon Snow focuses instead on the outside threat, the white walkers, which puts the North in the best position to survive.
Secret Information in the Citadel Library
We see Sam Tarley in the Citadel, the greatest library in Westeros. All kinds of information that is vital to the humans is literally locked up in the Citadel. The maesters there are keeping the “memory” alive, but not making that useful information available.
Be transparent with your information, don’t horde it. You never know who needs that data to help them do their job.
Development practices like Test-Driven Development can lead to high levels of Unit Test coverage. Sometimes, the team reaches 100% statement coverage. How can testers add value when the code is “fully covered”?
Example of a project with 100% Unit Test Coverage
I provide a few examples in this Sticky Minds article:
Review unit tests for missing cases. Just because the code is fully executed doesn’t mean all of the cases are used which might cause the code to fail.
Review unit tests against the product requirements. The unit tests will check that the code works as the developer intended. Sometimes, you can verify that the functionality meets the requirements.
Review the unit tests themselves. Having 100% coverage for unit tests means that the code was executed during a test, not that the tests are good, or even test anything. Check that the assertions are valid and useful.
Review Exception Handling. Unit testing is a good way to test the exception handling because the developer has full control of the mocked environment and can simulate the exceptions. These exceptions are difficult to inject in other types of testing, so making sure the unit tests do a good job is important.
Other ideas? Great, please check out the article and leave a comment either here or there.