Diagnostics

16 articles

Test Automation Meets Simulation

By Paul Henderson I'm seeing increasing interest from many companies in using simulation environments with test automation systems to accelerate the testing process. Specifically, putting Wind River Test Management together with Wind River Simics is getting creative juices flowing in industry thought leaders. Why? Well, development teams have started to realize the benefits of simulation systems for speeding and validating system…

Wind River and IBM Attack Software Quality

By Paul Henderson As I've mentioned before, we've been working with IBM Rational for some time around quality management automation. Both companies see the skyrocketing software content and architectural complexity in the embedded device market as creating a tipping point where companies will not be able to continue with business as usual. Product development teams will need to take a…

Test Driven Development Meets Continuous Integration

By Paul Henderson In my last posting I mentioned I'd be running a webinar with James Grenning on Agile testing. James is a recognized expert and frequent speaker on the topic of software development and one of the original authors of the Manifesto for Agile Software Development. We talked about the case for agility where today's embedded software projects are…

Industry Investing in Better Device Runtime Visibility During Testing

By Paul Henderson Here’s the final installment in my series about our embedded device software industry testing survey conducted in April-May 2010 with almost 900 respondents (see previous blog postings).  If you’d like a copy of the full report in pdf, please drop me an email at paul.henderson@windriver.com and I will send it to you.In this section of the survey…

The High Cost of Poor Quality – Brand, Market, Budget

By Paul Henderson I’m continuing my series on our embedded device industry software testing survey conducted in April-May 2010 with almost 900 respondents (see previous blog posting).  If you’d like a copy of the full report in pdf, please drop me an email at paul.henderson@windriver.com and I will send it to you.In this section of the survey we asked participants…

Inadequate Management Visibility into Quality is Eroding Confidence

By Paul Henderson Here’s the next installment in my series on our embedded device software industry testing survey conducted in April-May 2010 with almost 900 respondents (see previous blog postings).  If you’d like a copy of the full report in pdf, please drop me an email at paul.henderson@windriver.com and I will send it to you. In this section of the…

Compressed Schedules Driving Shorter Testing & Defect Resolution Requirements

By Paul Henderson Today I'm continuing my series on our embedded device software industry testing survey conducted in April-May 2010 with almost 900 respondents (see previous blog posting).  If you’d like a copy of the full report in pdf, please drop me an email at paul.henderson@windriver.comand I will send it to you.In part 2 of the survey we asked about schedule compression…

What’s New in Wind River Test Management 3.3?

By Paul Henderson Today we announced the latest version of Wind River Test Management, Release 3.3, our test automation system for monitoring, executing and managing embedded device software testing. Wind River Test Management lets teams optimally execute complex tests while dynamically gathering information from the production software under test as it is running, without requiring special pre-instrumented software builds. This…

Wind River @ IBM Rational Innovate 2010

By Paul Henderson Today marked the opening of the annual IBM Rational Software developer conference, this year called Innovate 2010, here in Orlando Florida.The 4 day event is covering a range of topics on both IT and embedded systems software development and test lifecycle tools and technologies. Wind River has a presence on the exhibit floor and a number of…

Quit Bugging Me: Revalidated

By Mike Deliman One day, I get this phone call. "We're working with the system, we see the calls that update the exception handlers early on - connecting the clock routines, etc. Then not very much farther on we see the system has run past where tasking should be running but it's not.  When we check, we're not getting any…