Every software development team or company will come to the point where a test automation tool is needed to downsize the effort of regression testing. The test automation tool can help the tester and the whole team to concentrate on other important testing tasks that a tool can’t handle.
Selecting a tool sounds easy at the first look. Many people will pick the most used tool on the market or the one that supports the programming language of the product. Sure, these are two important factors when selecting a tool, but there is much more to consider when searching and selecting the tool.
Different Types of Test Automation Tools
But where to start? When deciding for a tool, it’s important to know the different types of test automation tools and how the tools are working on a high-level view. Basically, there are five different types of test automation tools on the market:
- Image recognition: Tools in this category are taking screenshots of the UI elements in the product. The screenshots will be added to the automation scripts. With the help of the screenshots the application under test will be automated and verified.
- Coordinate based recognition: With the help of x/y coordinates, tools in this category are interacting with the application under test to automate and verify the application.
- OCR/ text recognition: Optical Character Recognition (OCR) or text recognition tools are able to identify elements based on their given text. The tools use the visible texts to drive the automation and to verify the application.
- Native object recognition: Tools that use the native object recognition detect the control or UI elements on their given element tree. In most cases this tree is built by CSS, XPATH or XML to identify, automate and verify the elements.
- Capture & Replay: Tools in this category offer a convenient and easy way to record the automated scripts. Every interaction on the screen being it scrolling, tabbing/ clicking or typing will be recorded and translated into automation steps for the tools. The recorded scripts can be used to replay the activities and to verify the application under test.
Some of the available tools on the market support more than one recognition approach. Sometimes this might be useful to combine the approaches in the automation scripts to get more robust automation scripts.
If you want to, how to select the right test automation tool for your team, read my latest blog post at https://blog.testproject.io/2019/03/11/how-to-select-the-right-test-automation-tool/
Increasing adoption of methodologies such as DevOps and Agile testing proved to be one of the key software testing trends that was seen in 2018. With the advancements of information technology, the software testing industry is also evolving at a fast pace. Modern software development teams are no longer content with the testing phase of a software to happen as a last-minute affair. With DevOps being adopted by modern day software development teams, here are some of the latest trends in software testing industry that need to be adopted by a QA, tester in 2019 to continue to remain competitive among peers and to stay ahead of the competition.
1. Quality Assurance Will Drive DevOps
The fundamental idea behind DevOps is centered around achieving a seamless and end-to-end collaboration among the QA team, the programmers and other critical teams such as IT and back-end team of a business organization.
A very important portion of the product development is now being handled by the testing team, as developers being increasingly involved in building the application, unit testing, fixing the identified defects and overall maintenance of the application.
This is resulting is a much greater speed of quality assurance. Code deployment is being fueled by DevOps which is ultimately resulting in higher ROI and cost-efficient software testing. Read more
In the past, software products was planned, developed and tested for years until the product was finally released to customers. During the long planning and implementation phases many things can change from the used technology to the customer needs. Due to the changes or problems that need to be handled in later phases, companies lost a lot of money because of the slow and wrong project management approaches.
However, things have changed since the year 2001, when the agile manifesto was introduced to revolutionize software development. The agile manifesto contains 12 principles with a clear focus on the customer, the software delivery, the collaboration inside a team and the outcome rather than processes and documentation.
Now, 18 years later since the agile manifesto was introduced by a group of software developers more than 70% (according to PMI) of all organizations use agile methodologies such as SCRUM and KANBAN.
In this article I want to focus on the agile methodology of SCRUM and why SCRUM matters for you and your company.
With the launch of modern smartphones in 2007 and one year later with mobile app stores, software products are used by their customers from every possible location. Furthermore, the products must serve the users’ needs wherever they are and whenever they want to use it. With the rise of high quality mobile phones and products the expectation from the software increased. Users are way more emotionally attached to their mobile phones and to the software that runs on it.
But what has this example to do with SCRUM? Read more
Since 6 years the state of testing survey is conducted by PractiTest’s QA Intelligence Blog in collaboration with TeaTime with Testers.
Over the last years the survey provided unique insights into the testing craft around the world and helps us to shape our
work and community.
I highly recommend you take some minutes and to fill the survey to provide yet another awesome report for all of us.
Please follow this link to fill the survey!
Once the survey results are live, I will let you know on my blog.
Agile methodologies such as SCRUM and KANBAN are the most used frameworks within small and independent software development teams. In theory SCRUM and KANBAN are really easy to establish in teams and companies. However, the majority of software development and product companies have more than one development team working on the same product at the same time. Does that mean companies with more than one development team can’t establish agile methodologies?
Of course not, but companies need to have the right environment and the right mindset inside the company to scale agile software development across all disciplines.
Scaling Agile Development The Right Way
The first piece of puzzle every company has to find is the north star. With the help of this product metric, the company can define its vision and mission. This will help the software development teams in terms of guidance, stability and focus.
The next part of the puzzle is the development infrastructure. It must be modern built up on the latest technologies and patterns to build a microservice architecture to provide agile teams the possibility to release whenever they want independent from other teams inside the organization.
Last but not least, it’s important to keep the agile development teams small and as independent as possible. With the help of agile coaches, the right agile mindset can be established inside the team. Once all of this is in place, it’s time to scale across the organization.
Read more about this topic in my lastest blog post I wrote for Applause here: