Posts

Showing posts with the label automation

Trends 2022

 Where has the last year gone?  It is time again to review yearly trends in software testing!  Decent read: intro to top 6 below; I know the suspense for the others will be overwhelming. Geeks2 top-10-software-testing trends 1. IoT Testing - everything is connected. See #6 2. Codeless Automation - is this finally the year for a major shift?  History says “no”. 3. Blockchain - follow the $$ 👍🏻 4. Big Data - is this finally the year for gold in big data?  Find smart data analytics people yet. 5. Performance Engineering - speed is king 6. Cybersecurity - true #1

ARE: automated and English text software test translators; ARE NOT: Linguists or Localization translators

Welcome!  To clarify the most significant confusion our viewers face, let me clarify the current KLOMAR focus: KLOMAR can translate your automated software tests (Selenium, RPA, test data, and others) and English language manual software tests into new automation languages or standardized common language English manual tests. KLOMAR does not do language localization or linguistic services. Please let us know how we can assist - even if it is beyond our current focus.

Review and executive summary: Five reasons test automation projects fail by Ford Arnett

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

Breaking down the Software Test marketplace

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

Kobiton Software Test Survey

Kobiton Press Release Summary of Software Test Survey: 55% said automation would improve software quality 76% are currently automating fewer than half of all software tests 85% said they’d like to automate at least a quarter of all test cases eventually 58% said their automation programs are relatively new or at least six months from beginning 26% are struggling with the process of evaluating and choosing the appropriate test automation tools  17% have found it challenging to train and acquire skilled automation engineers 73% are manually running at least 100 tests prior to each software release 51% are releasing software updates daily or weekly

Re-starting the software test optimization conversation.

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!

Regex skills for testers

Software testers can use regular expressions ( regex ) for test data generation and test tools.  A useful site for learning, generating code, and checking your regex is Regex101 .