Free AI web copilot to create summaries, insights and extended knowledge, download it at here

Abstract

UI, elements layout and make sure that users have a good experience.The only problem with that is they are less technical in many cases and might be not aware of how the app works in general. They might understand what is the logic behind a single feature, but they might miss a bigger picture.For example, those are the things they might miss during the design phase:<ul><li>Negative testing and error screens. Designers frequently miss the cases where something goes wrong (e.g connection is lost, the user is banned, application crashes, etc.), and our job as testers is to remind them about those cases</li><li>Designing only for a few screen sizes. Mobile development requires knowledge of different screen sizes and resolutions. Some designers miss that part and only create their mocks for specific screens. Make sure to communicate with them about those things</li><li>Design Overthinking. This is a harsh truth, but designers frequently come up with too many screens, buttons, and extensive logic, and in some cases, that’s not really necessary</li><li>Lack of technical knowledge. Software Developers and Software Testers are typically aware of the limitations of the app and what could work properly. Only the tight collaboration between QA, Developers, and Designers could lead to a proper application design at the end.</li></ul><h1 id="46d5">This deadline will be missed</h1>There is always pressure when working in a team. It’s either that deadline that’s approaching too fast or maybe a boss that thinks that implementing a feature could take a couple of days instead of the month.If you are a Software Engineer — most likely you understand that’s it’s nearly impossible to release the feature in that time frame and make it fully functional unless you are expected to work 24/7.If you are QA Engineer most likely you get the idea about it too either from personal communication with Developers or from your own calculation. Just be realistic and helpful with a development team. If you could start testing early — start doing so.Test whatever you could and provide feedback. Even if the deadline is missed at the end —

Options

at least you have done all you could to make the feature mature enough for a release.<h1 id="b6d8">You are much more than a Test Engineer</h1>Once you start working as a QA Engineer and gain some knowledge about the product and services — you will realize that you can help in much more ways than just testing. Among those things are:<ul><li>Technical Support. You know the product and you should be able to help the real users to resolve their problems</li><li>Helping hand for designers. You are the stop-gate between designers and a development team. Not all the things are possible to implement (especially, on a tight schedule) and you should highlight that.</li><li>Developer. Sometimes the feature is simple and requires small changes. As a QA Engineer, you might have enough knowledge to fix small bugs yourself.</li><li>Release Engineer. When it comes to releasing the build — you might be the one who does that as well. Especially in the startup environment.</li></ul><h1 id="f2cf">Don’t forget about your QA Team</h1>If you are working with a team of QA Engineers — make sure that you have the proper communication within a team.In my experience — every QA Engineer is unique. We use the application differently and we might come up with an extensive Test Plan together. You could be the only warrior in the QA Team, but if you have more people — the testing becomes much more fun.It’s always a good idea to have good communication within a team. It pays off in the end. Trust me.<h1 id="14f2">Conclusion</h1>Test Engineer in 2021 and beyond is much more than a person who does testing and reports the results. You are expected to be proactive, efficient, and know many areas of the product.Software Testing is not always a smooth ride. You should expect some turbulence along the way and a lot of communication between Product Managers, Designers, and the Development team itself.The main thing to understand is that Software Testing those days is as much important as the development process. There is not much trust in applications that were not tested properly. Simple as that.</article></body>

5 Confessions of a Software Test Engineer

Photo by Christina @ wocintechchat.com on Unsplash

I’ve been a Software Test Engineer for over a decade. I’ve worked with small and large teams and over time I’ve accumulated many things that I love about this area of work.

Working with talented people and helping create big products is among those. There is also a reality. It’s not good or bad, it’s just how things are happening when you are working as a Software QA Engineer.

This is a list of things that I’m personally aware of and those are my recommendations on how to make sure the software development process is smooth.

No, this feature was not yet tested

No matter how many times I’ve heard that the feature was already tested by the developer and only needs minor testing — this was either not true or partially true.

And I absolutely expect that. The developers only have tested a small part of the feature on their local environment, which means:

A local database
Rapid fast back-end, because it’s also running on local-host
Emulator instead of a real device (in case of Mobile testing)
Only one operating system and browser (in case of Web testing)
Only one type of the account
Lack of knowledge of other components of the app

If you hear that the feature is ready for testing and can be released to Production soon — take it with a grain of salt. Take your time and resist the pressure as much as you can.

You are the one who is responsible for the quality of the software. Do your best and try to cover all the main scenarios.

Focus on designers during the feature development

Designers are the people who try their best to come up with a proper UI, elements layout and make sure that users have a good experience.

The only problem with that is they are less technical in many cases and might be not aware of how the app works in general. They might understand what is the logic behind a single feature, but they might miss a bigger picture.

For example, those are the things they might miss during the design phase:

Negative testing and error screens. Designers frequently miss the cases where something goes wrong (e.g connection is lost, the user is banned, application crashes, etc.), and our job as testers is to remind them about those cases
Designing only for a few screen sizes. Mobile development requires knowledge of different screen sizes and resolutions. Some designers miss that part and only create their mocks for specific screens. Make sure to communicate with them about those things
Design Overthinking. This is a harsh truth, but designers frequently come up with too many screens, buttons, and extensive logic, and in some cases, that’s not really necessary
Lack of technical knowledge. Software Developers and Software Testers are typically aware of the limitations of the app and what could work properly. Only the tight collaboration between QA, Developers, and Designers could lead to a proper application design at the end.

This deadline will be missed

There is always pressure when working in a team. It’s either that deadline that’s approaching too fast or maybe a boss that thinks that implementing a feature could take a couple of days instead of the month.

If you are a Software Engineer — most likely you understand that’s it’s nearly impossible to release the feature in that time frame and make it fully functional unless you are expected to work 24/7.

If you are QA Engineer most likely you get the idea about it too either from personal communication with Developers or from your own calculation. Just be realistic and helpful with a development team. If you could start testing early — start doing so.

Test whatever you could and provide feedback. Even if the deadline is missed at the end — at least you have done all you could to make the feature mature enough for a release.

You are much more than a Test Engineer

Once you start working as a QA Engineer and gain some knowledge about the product and services — you will realize that you can help in much more ways than just testing. Among those things are:

Technical Support. You know the product and you should be able to help the real users to resolve their problems
Helping hand for designers. You are the stop-gate between designers and a development team. Not all the things are possible to implement (especially, on a tight schedule) and you should highlight that.
Developer. Sometimes the feature is simple and requires small changes. As a QA Engineer, you might have enough knowledge to fix small bugs yourself.
Release Engineer. When it comes to releasing the build — you might be the one who does that as well. Especially in the startup environment.

Don’t forget about your QA Team

If you are working with a team of QA Engineers — make sure that you have the proper communication within a team.

In my experience — every QA Engineer is unique. We use the application differently and we might come up with an extensive Test Plan together. You could be the only warrior in the QA Team, but if you have more people — the testing becomes much more fun.

It’s always a good idea to have good communication within a team. It pays off in the end. Trust me.

Conclusion

Test Engineer in 2021 and beyond is much more than a person who does testing and reports the results. You are expected to be proactive, efficient, and know many areas of the product.

Software Testing is not always a smooth ride. You should expect some turbulence along the way and a lot of communication between Product Managers, Designers, and the Development team itself.

The main thing to understand is that Software Testing those days is as much important as the development process. There is not much trust in applications that were not tested properly. Simple as that.