Software Test Optimization

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!

Let's Talk About Data Generators   by Rafaelo Condret REVIEW:  Good introduction to options for generating test data - worth the read if you are new to data generation or want to dig deeper.  Discussion topics include reverse regex, programmatic, and simple tools.    Generator Patterns: Boolean   —  this data type is one of the simplest and it’s used to define if a value is true or false Numeric Patterns —  the numeric patterns include many other data types (integer, long, double, etc.) Sequential —  will generate a sequence of values starting from one value and ending with another one Date and Time Stamp —  obviously, this will generate date and time formats Text Patterns  —  used to generate from one-word texts (first name, country, city) to more complex phrases (using Reverse Regular Expression Text)

Do you need datasets to run against your vision AI software projects? Color detection: Google-512 dataset used with robotic interactions and 11 colors. USC SIPI Image dataset   supports research in image processing, image analysis, and machine vision.   IMDB Wiki dataset for face detection. CIFAR-10x dataset for image classification.

Do you need custom test software developed or need to convert tests from one tool or format to another?  We specialize in these test development projects!  Contact info@klomar.com or respond to this blog entry for an estimate.

COVID-19 is clearly the most important test of the day and containing it is everyone's top priority.  Ok testers, in a language you can understand: IF ((you have had exposure to a COVID-19 positive person) OR (you have a temperature) OR (you have lower respiratory congestion)) THEN {       You should be tested for COVID-19       While awaiting a Negative Test        {                 Quarantine        } } Continue smartly! And in an abbreviated data-driven format: Exposure     Temp    LowRespCongest    Test/Quarantine Y                    *                  *                            Y *                    ...

Test procedures store most of the value generated by your test organization.  The defects they generate and the quality of your software ultimately determine the value of your test organization. All test procedures written in a spreadsheet (XLS, GSheet) and in data-driven ready format provides the most flexibility for ease of automation and future manipulation.  Procedures can generate text natural language procedure (from the concatenation of data/procedure) for manual testing.  Separate tabs or worksheets should be used for unique scenarios.  Embrace the data-driven paradigm and change the way your organization views test procedures!

On February 14th we asked for input on standard test libraries .  One of the examples provided shared 20 "scenarios" for Login pages.  As a starting point to standardize procedures, we will use these 20 test items.   The test items are really a checklist without specific procedures and data.  They are organized validly into GUI/Functional, Security, Session, and Configuration/Browser categories.  A state-based approach is recommended for consistently progressing through a collection of data-driven tests. How to create common data-driven procedures from this checklist (and/or from project requirements): 1. Identify what each checklist item is providing for a test procedure (DATA, VERIFICATION as a standard or extended procedure, or a GUIDELINE). 2. Define a standard procedure for each unique VERIFICATION and the variable DATA needed for that procedure. 3. Define rows in the data table to verify each item. 4. Define all steps to execute each procedure....

W3Schools ( https://www.w3schools.com/ ) is a great site for you to improve your web skills through interactive examples.  Great for manual testers to improve abilities for data-driven testing and automation.