Software testing: how does it work?
Every other week one of our employees writes a Bexter blog. A section with a variety of topics, from what's going on with the client and trends in the market to a look behind the scenes at Bexter. This week it is the turn of our software tester Petra. She writes about what software testing includes and how does it work.
My role as a software tester
Everyone has a different perspective on the testing of software. That makes sense. Everyone looks from their own perspective. One looks more at the appearance of the application, the other looks at the trendy aspect and the next looks at a specific subject in the application. For TrackOnline I look at the general picture, the additions and adjustments that are made and the ease with which the application can be used.
As a software tester I am part of the development team. My work consists of more than just testing the application. As a team we prepare ourselves together with the product owner for new assignments before they are developed. We receive new assignments through the business team or through our customers, but are also proposed by the development team itself.
Testing new features
For example, the business team came up with a request to add rental contracts for/per cargo carrier to TrackOnline. The team did research with customers and in the market beforehand. A complete description is provided that the business team believes the rental contracts must meet. This proposal is then discussed by the development team and the product owner. All kinds of questions are asked and answered until there is a clear picture of what needs to be developed. In case of an extensive subject such as lease contracts, we choose to divide the subject into small clear documents. This makes the development easier and ensures a quick delivery.
Another example is that a client indicated that certain information could not be added to 'Location detail'. The business team then investigated whether more customers were missing information in this part of the application. We recently added 'Name shortened' to the 'Location' screen. In the location overview this new information is also visible in a column and can be searched for. A nice addition for TrackOnline. We have also made it possible to hide fields in a transaction at the request of customers. We have developed Custom forms for this purpose. This way the customer can determine which fields are filled in on the transaction detail. The configuration has been made very simple, so the customer can arrange this himself. The possibilities depend on the chosen TrackOnline license. The Custom forms are expanded step by step. For example, the customer can now specify a date range or a fixed date, and an item configuration can be chosen. Other added features can be read in the latest TrackOnline update.
We work in sprints of two weeks. In this way we deliver new functionalities and improvements with a constant flow. During the sprint, I work on the picked up topics. I check the result at an early stage. During testing it is important to me that the scenarios used for the development of the addition or modification work correctly in the new version. This means that I check whether the built environment corresponds with what we as a development team have agreed upon. All parts of the application are connected to each other. I therefore spend a relatively large amount of time checking the effect of an adaptation on the entire application. We want to prevent that a new functionality damages another part of the application.
Because of the development colleagues' technical knowledge, they can give me extra information that I can use very well during testing. This way I can go deeper during testing. It is also very valuable that I can contact the development colleagues if I come across issues that I cannot explain properly. Producing a perfectly functioning product is really a team affair.
I find it important and valuable to receive tips and comments from colleagues and customers. They look at the application in a different way and also use the application differently than I use it. This way we can find out mistakes quicker or make it easier to use the application. All tips and comments that I receive, I investigate and, if necessary, are processed into new topics that we can pick up during the development of TrackOnline.