October 27, 2010

Customers are the greatest source of new ideas

I spent two weeks in India visiting clients and prospects. Clients came from a number of industries like civilian aerospace, automotive and telecom. Lots of auto clients strategizing what to do about ISO 26262. The temperature was comfortable - not too warm, not too humid. It was especially nice in Bangalore, which is located relatively high above sea level. I also saw that the metro system is progressively falling in place. I can't wait to try it - we have several clients in the Bangalore area and traffic is a major issue (Indians will readily confirm this). Based on previous experience, a metro will really help move things along (pun intended). I also took this picture during a... Continue reading »

Posted by Steve Barriault in VectorCAST In Action

October 25, 2010

A Testament to VectorCAST Openness

I visited a long term customer in Toronto this week that has developed a really sophisticated test environment built on top of VectorCAST/Ada, VectorCAST/C++, and multiple different target RSPs. They have been a customer for more than 10 years and have built a really interesting test environment which allows them to automatically run the same tests on a variety of live hardware boards. Their infrastructure provides similar functionality to that provided by... Continue reading »

Posted by John Paliotta in VectorCAST In Action

October 22, 2010

What NOT to do during test creation

Are there designs that you should avoid using in unit tests? The answer is going to vary depending on your particular source code, but setting up your tests carefully will make them easier to maintain! If you are interested in some examples, James Carr came up with a list of test anti-patterns.

Posted by Shelly Chang in Coding Standards

October 19, 2010

Ship now, test later?

For as long as there has been computer programming there has unfortunately, been a general shortfall in the amount and quality of testing required to ensure a consistent high level of product quality and reliability. There are four primary reasons for this shortfall: Cost Testing is inherently labor intensive and inefficient and therefore inherently (until recently) expensive; and as a general rule of thumb, component testing requires generating one line of test code for each line of component code to be tested. Schedule and Staff Constraints Project schedules typically provide insufficient amounts of time for testing. In addition, the staff assigned to testing tend to be insufficiently experienced in testing requirements and... Continue reading »

Posted by Michael Rielly in Coding Standards

October 06, 2010

ISO 26262, Next Exit

I visited with a customer in Europe last week that is building an engine electronic control unit (ECU). They are currently preparing for the new 26262 standard for automotive software development. We had a great meeting! They indicated that two years ago, one of their development teams was mandated by the customer to do unit testing. The team saw real benefits from testing and now perform unit testing even when testing is not mandated by the customer. They feel that they are well prepared for the coming 26262 requirements and we were happy to hear that they are planning to use VectorCAST as a key part of their... Continue reading »

Posted by John Paliotta in VectorCAST In Action

October 04, 2010

The Beard of Experience

Happy Monday! Here's another great cartoon from Cartoon Tester.

Experience comes with years of hard graft, countless night researching ideas, thousands of raised defects, and decades of honing your craft...but a beard can be grown in a few months.

I wonder if a goatee counts. ;)

Posted by Michael Rielly in