Re-starting the software test optimization conversation.

Let's start the conversation with these questions:

  1. How would you describe your software test methodology? Agile, structured, ad hoc, custom, or other.
  2. Approximately what percentage of your software tests are automated?
  3. What are your software test automation tools?
  4. Which software test environments are all used? embedded, desktop, web, apps, IOT, other.
  5. What test levels are all formally documented in your software test scope: unit/module, build, functional, system (structure rather than test type)
  6. Do you have a formal test strategy or process document guiding your test planning?
  7. What are your priorities and goals for test improvements? (such as maintainability, new function efficiency, or defect reduction)
After baselining your current test state, the next step is digging into a deeper review of a recent test project's test documentation and assets.  Contact KLOMAR to take the next step!

Comments

Post a Comment

Popular posts from this blog

Don't Let This Be YOU: Mazda bricks Radios with Software Defect

Image
 ARS Technica article on Mazda radio defect by  JONATHAN M. GITLIN  -  2/9/2022 SummARY: A critical real-time defect in Mazda radios was triggered by a Seattle radio station.  If you were unfortunate enough to have this  2014 to 2017  Mazda radio and live in the Seattle area listening to  94.9 FM , the radio was no longer usable.  Files with no extension were (like .jpg) were the use case that sent the radio into constant reboot condition rendering it useless.  Read the full article at link above.  Yes, I was slow to find this gem.  Please share if you find more like it!
Read more

F35 System Testing

Image
Many calendar years of development and testing have gone into one of the most complex vehicle systems ever -  the F-35. This article details how performance and  End User / Operational Testing of F-35  is being performed.
Read more