Wire harness development and testing Slow is painful by Jon M Quigley Vehicle Systems Vehicles have become increasingly electrical over the year, even vehicles that are not electric propulsion. There are more features, more embedded controllers and greater communication between the electronic controllers. The range of content is from power electronics, sensor data (analog signals), […]
Posts Tagged
‘testing’
By Jon M. Quigley I saw a LinkedIn post yesterday about scope of testing during times of compressed schedule. The position was to test what is new in the software, and of that new, what is the most important, perhaps meaning what if it goes wrong, would be the worst for the client or customer. […]
Why formalize root cause analysis? There are many approaches to determining the root of our problems. In the automotive world, there are two typical approaches, the 8D or the 8 Discipline, or the A3 (named for the paper size). We will not go into the details of either of these approaches but you can find […]
We are composing a glossary of test terms and we take one from that work today and discuss here. A development organization can be structured in many ways. The development and testing can be essentially one department under one management structure, or these two areas, development and test can be separated each with a respective […]
There have been some twitter discussions going on about the validity of the term end-to-end (E2E) testing. I have been around this concept for many years and still see the validity in the term and the approach. To that end, I will describe as quick and briefly as I can since this is a blog […]
Verification and Validation The definition for verification and validation can be found at[1]: We must express some disagreement with the activities associated with the individual areas. For example, testing is not limited to Validation. Testing is also a function of verification as we will use these techniques to understand if the instantiation of the […]
Testing Complex and Embedded Systems What set of conditions could cause this event to occur? When we have elicited all we can from the customer about fault information, it is time to proceed further in our analysis. This next step requires investigation of the design to understand how the symptom of failure described could happen […]
Project Closure and Team Disband One of my favorites and often poorly executed part of a project is the project closure. Project closure is not just a simple wipe our hands together and smile, then proclaim that we are finished with the project. It is not even handing the customer our results and patting everybody […]
Regression Testing and Scope A brief exchange on twitter on the topic of regression testing leads me to this post. Twitter, is not the place to really discuss this topic as there are too few characters and there are many factors that go into determining the scope of regression test. Regression testing is the testing […]
Poor Excuse for Not Automating Testing Recently I came across and participated in a social media exchange that proposed that automating product testing (software) was really not helpful. Their assertion was backed with comments about personnel new to testing will be unable to learn how to test. Testing and System Complexity System and software complexity, […]