Qa Random Questions

Front 1

Tell me about your day at work

Back 1

09:00 turn on my laptop, open your email and Slack to check any urgent messages

09:15 “Stand-up meeting” (15 min) to discuss what you're working on today and hear others

09:30 check emails and my assigned test-runs (*multiple test cases) (“test plans”) execute test cases, mark as Pass/Fail

12:00 lunch (+a walk)

12:45 keep executing the test-runs Or work on my assigned tickets Or write more test cases (after finishing "test plans")

1:30 raise (created) bugs/defects (if test case is “failed” or you found an issue)

2:00 “update/add test cases if necessary”

3:00 go through assigned tickets to verify if fixed or not

5:30 complete daily status report (usually once a week, on Friday)

6:00 Finish working ;-)

Hint 1

10

Front 2

How big is your team? How do you communicate?

Back 2

My team has 2 QA testers, a QA lead, and QA Manager.

Mostly communicate in Slack and email.

In case we have meetings (video/audio meetings) with my team or other teams online, we meet in Google Hangouts.

We have daily stand-up meetings, where we discuss problems, what we're working on and updates.

We also communicate regarding the issues in the comments of Jira tickets.

We work closely with Dev and Product Management on which tickets must be prioritized/verified/reopened/closed or to clarify expected and actual behavior.

Hint 2

1/5

Front 3

How can you describe the QA process in your company? Tell me what QA Engineers do in AGILE SDLC.

Back 3

It's Agile, We start with Test Planning and Test Development.

Our team writes test plans & test cases based on the requirements.

Then we do Test Execution and Bug Reporting, Executing and maintaining the test cases.

Marking them as pass or failed, and if it failed we create bug reports.

We start the day by reading emails, messages, stand-up meetings where we discuss cases & issues we are working on.

Verify implementation of requirements by executing test cases and creating bugs in Jira if we find issues.

Then we do Defect Management, Verify bug fixes, Close the bugs if they are not reproducible or reopen them if they are reproducible with our comments with actual results in both cases.

Hint 3

7

Front 4

What devices do you test first?

Back 4

Usually, the company provides a list of devices and OS by priority.

I will test the highest priority devices first (P1) and if we have enough time and resources will test P2 later, usually, we don't have time for non-P1 devices.

This priority is based on a business document that lists the most popular devices used by the users of the app.

Hint 4

3

Front 5

What is the difference between Mobile and Web testing?

Back 5

In Mobile: - I check Installation, Interruption (calls, messages, notifications, battery charge),

- Different Memory size, battery power consumption, portrait/landscape (vertical/horizontal), input method(keyboard), swiping, navigation, screen size, the mobile network: 2G, 3G, 4G

- Mobile Apps can work without an internet connection;

- Device fragmentation (for example: In one company like Apple/Samsung there are many devices/systems/versions)

In Web: - Cross Browser Testing and Compatibility Testing

- Don’t need to install app on the device

- Web Applications are more vulnerable to hacks compared to the Mobile Apps

Hint 5

7

Front 6

What is the difference between Smoke and Regression testing?

Back 6

Smoke Testing is performed to verify that the critical functionality of the program is working fine.

Regression Testing is a type of software testing to confirm that a recent program or code change has not affected existing features.

Hint 6

2

Front 7

How do you perform GUI (UI) testing?

Back 7

According to requirements, Design Document or based on GUI standards, to make sure all looks and feels good, nothing is overlapped, misaligned, truncated.

Everything must be aligned, have correct grammar and format (color, size, font).

No grammar or spelling mistakes, Everything is consistent and easy to read.

Hint 7

3

Front 8

How many bugs did you write on average per day? What was a recent one?

Back 8

It depends, on a regular day it was 5-7, but if we had new features or pages it could be more (10-12).

Hint 8

1

Front 9

Describe one big bug that you found in your project? What is your biggest/most interesting bug?

Back 9

Great question, I found many interesting bugs on a daily basis, I don't remember most of them:

I had this time when After a user logged out, you could click “back” button and it would go back to the log-in page with private information of the user.

Hint 9

2

Front 10

How did you set a priority?

Back 10

Using common sense and the culture of the company, phase of the SDLC, place (main page or not), type (Functional or UI) of issue and priorities of the company.

Mostly functional issues were a higher priority than UI issues, and it also depends on where the issue is.

Hint 10

2

Front 11

How many test cases did you execute on average per day? How many test cases did you write on average per day? Tell me about recent one.

Back 11

It depends on the day, usually I execute 25-30 if I don't have other tasks to work on.

Sometimes more, sometimes less.

Depends on the day and the tasks, I write between 0-30.

Hint 11

3

Front 12

Name Test case components

Back 12

Test Case I.D., Title/Description, Pre-conditions, Instructions, Expected Result, Actual Result, Status

Hint 12

7

Front 13

Tell me about your company's sprint cycle. How long was it?

Back 13

We have a 3-week sprint cycle, We start with Planning before the Sprint.

After Sprint starts - we have functional testing for about 2 weeks, following “code freeze” when developers are ready to turn the code over for testing.

After that we do Regression for about 3-4 days and release, followed by Sanity Test (or Smoke Test) on production.

*Planning > Functional testing (2 weeks) > “Code freeze” > Regression (3-4 days) > Release > Sanity test*

Hint 13

3

Front 14

What would you do if you don't know what to do and you're stuck?

Back 14

I will investigate the documentation. If I don't find the answer, I will search for it on YouTube or Google (~20 min).

If I can't figure it out by myself, I'll ask another QA person or the QA lead.

If they don't know the answer I'll ask the QA manager, relevant Developer or the Product Manager. When I get the answer I'll add it to the knowledge base document.

Hint 14

3

Front 15

What can you bring to the company?

Back 15

I can help deliver a quality product and a better user experience for the customer.

I am detail oriented, hardworking, a good communicator, a quick learner, and a multitasker.

I can bring great results to the team and improve test coverage.

Hint 15

3