QA INT questions part 1

When do you report issues in Jira?

I report issues in Jira when I see a mismatch between actual and expected behavior

What do you focus on while performing UI testing

I check that nothing is overlapped, misaligned, or irregular font size. No spelling or grammar mistakes.

Tell me about your company/project/job

Reelly AI is a platform that uses AI to help real estate agents and developers speed up property sales

Tell me about your project pt 1?

Software QA engineer for Reelly AI, i participated in user authentication & access control by creating test accounts and performing negative/positive testing with permissions.

Tell me about your project part 2

Used TestRail to write and execute test cases by cross-checking real project details against expected data. Also testing form inputs for creating/editing listings.

Tell me about your project part 3

Performed functional and UI testing for Reelly AI mobile and web applications through cross browser testing. Used JIRA to write bug reports and verify bug fixes. Maintained a regression test list throughout my internship.

How did you write a bug report?

1. Jira - create new ticket

2. I - issue type

3. T - title

4. D - description

5. E - environment

6. P - Priority

7. A - attachments

What do you do if the developer tells you that it’s not a bug (or as designed)?

Double check requirements, reproduce steps

Expected behavior, close bug

Not expected behavior, reopen & assign w/ comment

If requirements aren’t clear or missing, will ask product manager

What kind of comment do you leave if it’s as expected?

“As designed” or “not a bug”

What kind of comments do you leave if it’s against the requirement?

This is a valid bug/issue according to the requirements (PRD/Design/BRD/Specs) page 27 line 7

What kind of requirements did you work with? How many pages did your PRD have?

Our PRD design is about 25 pages. Usually located on google drive, its shared within our team, we can access it with our gmail.

What are possible reasons a bug can be marked as “not a bug”

As designed, cannot map to the requirement or test case

Low priority, not addressed

This is story, not a bug. (User just wants the feature to be enhanced)

Soon be redesigned

Management doesn’t consider it a problem

What will you do if the developer tells you the bug is not reproducible?

I will try to reproduce bugs on the reported device, following the correct steps, environment, device, platform, build

I will try to reproduce on 1 or more devices

If not reproducible, I will close the ticket and leave a comment

If reproducible, I will reopen the ticket and assign it back to the developer w/ comment

How can a tester be sure that a bug has been fixed?

tester can reproduce on new build and verify that the bug is no longer reproducible

How do you write test cases?

I - ID test case ID

T - title/Purpose

P - pre-conditions

I - instructions

E - expected result

A - actual result

S - status: pass/fail

Where did you write test cases?

I write about 25-30 cases a day in TestRail. Ex requirement: “Buy now” button, on the main page should be green

Describe the bug life cycle at your company?

cycle: open > in development > in QA > Closed/Done or Reopened

What would you do if you got behind schedule and you can’t finish your tasks on time?

I will continue executing test cases. Also, I will raise a concern to the QA manager that we might need more time and resources to finish this testing on time if i see that test cases are complicated or time-consuming.

How would you test an iPhone

first, I will ask for requirements because we create test cases based off requirements. No requirements: functional positive test cases.. does the device turn on & off, can I receive calls/messages, does the sound control works.

How would you test an iPhone part 2?

second, by focusing on functional negative testing: verify that phone will not ring on silent mode, verify that it doesn’t switch vertical/horizontal modes on lock mode, verify that you can’t unlock phone without a valid passcode/face ID/ finger print.

What is the difference between smoke and regression testing?

smoke testing is performed to verify that the critical functionality of the program is working fine. Regression testing confirms that a recent program or code change has not affected existing features.

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

It is about 3 weeks. Week 1: Planning & design. Week 2: development starts and while developers are working on the code, were working on test cases. Week 3: developers finish up the code and we start regression testing, following the release smoke/sanity testing is performed on production environment.

Why do you want to leave?

My internship ended and I am looking for a long term oppurtunity.

Tell me about your project (full answer)

Software QA engineer for Reelly AI

I participated in user authentication & access control by creating test accounts and performing negative/positive testing with permissions

I used TestRail to write and execute test cases by cross-checking real project details against expected data. Also testing form inputs for creating/editing listings.

Peformed functional and UI testing for Reelly AI mobile & web applications through cross browser testing. Used Jira to write bug reports and verify bug fixes. Maintained a regression test list throughout my internship.