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
About a month ago I wrote the following blog post about my mobile testing online course “A Beginners Guide to Mobile Testing” powered by Ministry of Testing. The complete course is now live at https://www.ministryoftesting.com/dojo/series/beginner-s-guide-to-mobile-testing-daniel-knott
In total the course is 1h 30mins long and will teach you the fundamentals of mobile testing. Please take a closer look at my last blog post to get the full picture what the course offers.
If you have any questions about the course let me know or take a look at the club, where you can discuss and share your learnings with other testers. Just follow this link to the club.
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: