Write test plans and make sure that the apps you work on continue to work properly
A quality assurance engineer helps guarantee consistent quality of an application by making sure that as new features are added they application they are a part of continues to work properly. The job entails a lot of writing tests and test plans, validating processes, and improving processes. You are the last "defense" before a new feature goes to production and it is up to you to make sure there as a few bugs as possible and that the code looks good before deploying.
The job requires a high level of organization and interest in knowing how an application works. Writing effective test plans is an art where the person needs to be curious in order to test all of the correct processes to ensure a high build quality. Good QA increasingly important as a firm grows, users use your software, and complexity of an application increases.
Learn more about some of the common tasks you will do on a daily basis in this role.
9 a.m. Start your day
Start your computer and begin your day
10 a.m. Standup
You have standup with your small team of other QA engineers. You talk about what you are currently testing and if you have any roadblocks that your co-workers could help you out with.
10:30 a.m. Write a test plan for a new feature
You were tagged in a pull request (a request to push new code into the application) and need to write a test plan for the new feature. You begin by pulling down the code to your computer and running through the new feature a few times, then deciding what areas of the code base it affects.
12:45 p.m. Write tests
Part of your job is to write automated tests that are run every time before the application is deployed. You tested feature you tested by hand previously in the week and need to start writing automated tests for it.
2:15 p.m. Check in with co-worker
Your co-worker said they were having some troubles with a part of your application you are familiar with. You two quick jump on Hangouts to chat and walk through the issue.
2:45 p.m. Give thumbs up for pull request
You give the go ahead on a pull request for the feature that you wrote the automated tests for. The other developer now has permission to merge their new code into the code base of the application.
4:30 p.m. Begin testing by hand
You start testing by hand the feature you were writing a test plan for this morning.
5:30 p.m. Finish your day
You take notes where you were in your testing and sign off for the day.
Get the latest information on starting a remote career with our newsletter. Sign up below.