Software Test Optimization

Full ariticle :  Five reasons test automation projects fail  from FierceElectronics.com by Ford Arnett If you are about to embark on a software test automation investment, this is a SHOULD READ, and if you aren't - this is a MUST READ to get you going down the automation path! Summary: " Test automation... has an alarmingly high failure rate. Often, this is due to unrealistic expectations, lack of understanding around automation, or not putting enough focus on value." Key Points: " 1. Forgetting automation software is still software" - manage it like other software development.  Have standards, schedules, set deliverables, version it, test it, and re-use - re-use - re-use (don't reinvent if you can help it). "2. Automating ‘just because’" - prioritize functions to be automated and start with high-value tests with the largest time savings. "3. No organizational support" - set the right expectations with all stakeholders. ...

A worthwhile read to understand where software test $40B USD$ are spent but nothing earth-shattering here (summary segmentation below is most of the story): Software Quality Assurance (SQA) Testing Market Set for Rapid Growth and Trend 2020-2026   by basavraj July 21, 2020 Software Quality Assurance (SQA) Testing Market Segment considering Production, Revenue (Value), Price Trend by  Test Consulting And Compliance Quality Assurance Testing Application And Software Testing Risk And Compliance Testing Covering OthersMarket segmentation, Market Segment by Consumption Growth Rate and Market Share by  Application: Artificial Intelligence Testing Cybersecurity Testing Blockchain Testing IoT Testing

Let's start the conversation with these questions: How would you describe your software test methodology? Agile, structured, ad hoc, custom, or other. Approximately what percentage of your software tests are automated? What are your software test automation tools? Which software test environments are all used? embedded, desktop, web, apps, IOT, other. What test levels are all formally documented in your software test scope: unit/module, build, functional, system (structure rather than test type) Do you have a formal test strategy or process document guiding your test planning? 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!

REVIEW: " Debunking Five Common Automated Testing Myths BY   ELYSIA LOC K  of DevOps Practice " Summary: Although " automated testing is imperative for DevOps maturity and success", many things hold us back from achieving success with automation, and among these (mis) beliefs and issues are: 1. " We Don’t Have the Time to Slow Down and Add Automation" - many organizations have proven the investment in smart automation pays dividends over time. A few general examples... 2.  " Automated Testing Is Too Difficult and Frankly, Just Not Worth It " -  start with high value low hanging fruit and make a solid foundation for growth. 3.   "We Have to Hire a Specialized Person" -    I will take the counterpoint here and disagree.  I believe that although most people in your org likely can learn and start to automate, THIS IS THE MOST IMPORTANT part of your automation strategy, DO NOT RE-INVENT THE WHEEL .    If you do not have a pe...

REVIEW: 3 Test Design Principles... by Melissa Benua This concise review of priorities and test strategy for continuous integration testing is highly recommended. Quick summary: 1. Reliability "If a test is only 99% reliable (one false report in every 100 test executions), and you run it 200 times a day, then your team will be investigating false-positive failures at least twice daily. "... 2. Importance ..."In a continuous integration system, the most precious resource you have to spend is engineers' time. Engineers have grown to expect results quickly, and they are unwilling to wait for something they perceive as wasting time. So ensure that you're getting relevant results back as quickly as possible."... 3. Specificity ..."But if you only have a budget of five minutes for an entire integration test pass, for example, and every integration test case takes 10 milliseconds, then you have time to run only 30,000 test cases. And if you ...