4 Most Common Myths Around Test Automation

  • Test Environment Setup:
  • Installing libraries using scripts
  • Setting configuration variables, etc.
  • Mocking Component Behavior
  • Useful in IoT & Embedded Software Testing
  • Can also reduce (or eliminate) actual hardware/component need
  • Test Reporting
  • Generating summary report/email.
  • Linking screenshots/logs to the reports.
  • Triggering emails on test execution, completion, etc.
  • Rerunning failures
  • It is helpful to automate the re-execution of failure/flaky tests.
  • It also helps to examine the consistency and probability of the failure.
  • Test Data Preparation
  • Creating synthetic test data
  • Creating dynamic & random test data
  • Scheduling Test Runs
  • Based on schedules
  • Based on continuous integration rules
  • Test Build Generation
  • Preparation of release candidates for testing
  • Updating results to ALM Tools
  • Ex: JIRA, Team Foundation Server, Polarion
  • Using API endpoints
  • Monitoring Production Logs
  • Comparing Files
  • Cleanup of Environment, etc.
  • One of the popular definitions of Quality is that it is “value” to someone “who” matters. Depending on context and personas, “value” and “who” take on different forms. Thus, quality is a multidimensional concept.
  • By performing checks through tools, Test Automation will help you find information. Having such checks will enable you to find regression issues.
  • With Test Automation, you can define checks to detect:
  • Functional Issues
  • Performance Issues
  • Security Issues
  • Accessibility Issues
  • UI, Responsive Issues, etc.
  • Quality will, however, mean different things to different people. Below are some typical software user personas:
  • Marketing Team
  • Tech Writers
  • Testers
  • Programmers
  • Managers
  • Customer Service
  • Business Specialists
  • Support/Sales
  • Different notions of quality will apply to your context according to the persona of your customer. Here are some of the possible quality attributes:
  • Reliability
  • Speed
  • Usability
  • Scalability
  • Maintainability
  • Testability
  • Documentability
  • Trainability
  • Functionality
  • Supportability
  • While you may be able to control some of these attributes, the majority are beyond your control or scope as a test automation engineer.
  • Newbies in test automation often focus heavily on the writing of test scripts.
  • Even though Test Scripts are one of the visible outcomes of test automation, there is more to it than that.
  • Automation engineers perform several activities that are often overlooked. They include:
  • Modelling application
  • Test data generation
  • Developing framework / reusable libraries
  • Work towards CI-CD-CT
  • CI = Continuous integration
  • CD = Continuous delivery/deployment
  • CT = Continuous testing
  • Documenting automation / Preparing readme documents.
  • Logging automation
  • Test design
  • Defining test execution strategy
  • Developing accelerator tools
  • Code review
  • Version controlling & tagging
  • Configuring / Parameterizing
  • What programming language do I need to learn to be successful in test automation?”. On a daily basis, I hear this question from people. Yes, programming has historically been at the heart of automation. It is no longer the only way to automate.
  • With the rise of no-code test automation tools, the obvious equation of automation = programming has changed.
  • Today, You can automate test execution using coded tools as well as no-code tools.
  • Automating reduces human intervention, and there are various ways and tools to achieve it without or with coding.
  • If you are new to no-code tools, you can check out Testsigma which is a popular open-source no-code tool Testsigma. Here is the link to the open-source version of Testsigma: testsigmahq/testsigma: Build stable and reliable end-to-end tests @ DevOps speed. (github.com)
  • Even if you are a beginner in the field of automation, no-code tools can certainly be used as a starting pathway for learning automation.
  • Test Automation = Automation Tools
  • Test Automation = No Manual Testing
  • Test Automation = Test Team Downsizing
  • Goal of Test Automation = 100% Automation

--

--

Testsigma is a completely cloud-based codeless test automation tool that lets you create stable and reliable tests for web, mobile & APIs — all from one place.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Testsigma Inc.

Testsigma Inc.

Testsigma is a completely cloud-based codeless test automation tool that lets you create stable and reliable tests for web, mobile & APIs — all from one place.