Software Test Optimization

 REVIEW:  How many developers does it take to test a product? September 28, 2020  by  Wayne Rash OVERVIEW: A collection of feedback from specific and named software organizations on how they form their development teams. Summary Quotes: " While in most cases, for every two to five developers, one tester would be fine..." "many variables come into play, ranging from  the availability of automation tools in testing  to the income reliability of the project, to how much of the testing can be automated" Software Criticality factor - "mission critical applications, including automotive, heavy truck, and mining equipment product development. A single failure could lead to death or disaster." Further thoughts from the reviewer:  We need a way to rate the efficiency and skills of test team.  AKA some warm bodies can reduce the efficiency of a test team.  We need consistency on how we generate test cases and determine coverage.  We need software ...

 REVIEW:  Konica Minolta settles lawsuit alleging flaws in EHR software for $500,000  by  ELISE REUTER  of MedCityNews "The whistleblower case alleged that an electronic health records company acquired by Konica Minolta cheated on certification tests to hide software issues." Summary: -" In 2015, Konica Minolta acquired Viztek , a North Carolina-based health IT company." -"Viztek allegedly hard-coded its software to pass certification requirements" (a.k.a. doing the Volkswagen) -Not a lot more details here, but another example of the length of deceit people and companies will go to hide defects rather than fix them.

https://github.com/USDepartmentofLabor/Mobile-Accessibility-Test-Script/blob/master/QA%20Test%20Cases.md These tests are based on  Best Practices by SSB BART Group  and on Level A and Level AA Success Criteria of the Web Content Accessibility Guidelines (WCAG) 2.0, W3C Recommendation, 11 December 2008,  http://www.w3.org/TR/WCAG20/ , as proposed by the U.S. Access Board,  http://www.access-board.gov/sec508/refresh/draft-rule.htm.This  checklist is inclusive of the Technical Standards of Subpart B of Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d),  http://section508.gov/index.cfm?fuseAction=stdsdoc . https://code.gov/projects/dol_opa_1_mobile_accessibility_test_script

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: 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 ...

Recruiting software testers into my previous organizations, I have always taken pride in identifying those with excellent test skills whether it be automation, customer validation, test planning, or any other skill required in a well-rounded test organization.  And believing I had a decent handle on those characters who may be suited for other technical positions but didn't have the drive and spine for my test org.  In my view, testers need to see things as broken and have a sense for when they see weakness there could be bigger problems ahead.  The water in that glass is 49.6% full and evaporating quickly! In contrast, software developers are notorious for believing all is good and no need to test in my code.  "If it compiles, ship it." That glass is at least 60% full! Clearly, the intersection of these viewpoints are brought together and everyone is asked to bring DATA for reality. Many jobs take a certain mindset and personality while on the job.  BUT ...

LILY HAY NEWMA N SECURIT Y 02.26.2020 04:59 PM How a Hacker's Mom Broke Into a Prison—and the Warden's Computer Security analyst John Strand had a contract to test a correctional facility’s defenses. He sent the best person for the job: his mother. Great story on security testing, that makes the general testing point: "Trust but Verify" applies to all types of testing.