Assessment Q&A Flashcards

1
Q

How does regression testing work?

A

When you receive a new build, you test the new functionality after this you also test existing functionality to ensure the new code did not negatively impact old functionality.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

How should QA analyst do requirement analysts and do test planning?

A
  • Review the requirements with the business analyst to gain a clear understanding of new functionality.
  • Document test cases that includes both positive and negative test cases.
  • Collaborate with the business analyst to determine field length and restrictions.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the standard test plan templet?

This is almost like asking what are a Test Plan

A
  1. Test plan identifier
  2. Test deliverables
  3. Introduction
  4. Test tasks
  5. Test items
  6. Environmental needs
  7. Features to be tested
  8. Responsibilities
  9. Features not to be tested
  10. Staffing and training needs
  11. Approach Schedule
  12. Item pass/fail criteria
  13. Risks and contingencies
  14. Suspension and resumption criteria Approvals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Are you aware of a complete work flow of the test life cycle?
(This is asking how does the STLC work)

A
  • Requirements analysis
  • Test planning
  • Test case development
  • Environment setup (any data needed)
  • Test execution
  • Bug fixes
  • Test cycle closure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is bug life cycle?

A
  • Understand the requirements
  • Log the bug
  • coordinate with the developer
  • Receive bug fix
  • smoke test
  • regression test
  • ensure that the bug is fixed (if it is close it if not reopen it)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

If developer rejects a bug what do you do?

A

Work with the business analyst to ensure code is not working as expected.

Clearly document steps.

If dev still rejects the bug, the business analyst should work with the developer to clarify functionality.

Inform leadership of disputed bug.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is Smoke Testing?

A

Smoke Test also known as “Build VerificationTesting”, is a type of software testingthat is comprised of a non-exhaustive set of test that is aimed at ensuring that the most important functions work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is Regression Testing?

A

Regression Test verifies that software previously developed and tested still performs correctly even after it was changed or interfaced with other software.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is Performance Testing?

A

Performance Test is testing done to determine how a systemperforms in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributeof the system, such asscalability, reliabilityand resource usage.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is Functional Testing?

A

Functional testing is a type of testing which verifies that eachfunctionof the software application operates in conformance with the requirement specification. This testing mainly involves black box testing and it is not concerned about the source code of the application.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is Web Service Testing?

A

From my understanding Web Service Testing making sure a user can send a request to a software service which in-turn returns a response in human readable format.

Basically making sure we can send & receive emails

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Can you tell me about yourself?

A
  • As a UAT tester I’ve worked with users on various platforms and operating systems like Windows 7 & IOS. I’ve tested web-based applications and a few client server applications like Salesforce. I’m familiar with and have written Test Cases based on requirement. I’ve attended requirement review meetings, at which I had to provide feedback to the BA and developers about defects. As for defects tracking, I’ve used Excel to track them.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Why should we hire you? (Look at the company’s need and how you can fill it)

A
  • In reviewing the job description there were two requirements that stuck out to me:

o One was that the candidate should have a good understanding of the UAT and regression testing. For the past almost three years these are the activity that I have performed. Not only do I have an understanding of them but I have the experience of doing them.

o The other point was that the person needs to have the drive to learn. This also fits my profile because I took the initiative to learn the testing process with over 200hrs. Currently I am learning Salesforce, so that I can get my certification, HTML5, CSS SQL so that I can improve myself professionally. These are all self-initiated.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What’s your weakness?

A
  • One of the weaknesses that I have is that I have not written that much Test Case in my role as a UAT tester. But I have taken courses and different exercises to challenge myself so that I am in practice and I’ve had my cousin review them because she is a QA Lead.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What’s your strength?

A
  • One of my strength is that I take delight in learning. I’m currently learning Salesforce in order to get my Admin Certification.
  • My other strength is that in my role Client Manager, I initiated a restructuring process for the way we presented information to the client so that it was more targeted and focused on their needs.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Where do you see yourself in 5 years?

A
  • That is a very interesting question because if you had asked me this question 5 or 10 years ago where I saw myself was a lot different than where I am now. I believe you can a make good analysis of the future my collecting data from the past. I started my career as a CSR and moved into the Product Development role within the same company. From there I progressed to another company to become a Project Manager. Through a change in course in my husband’s career, I find myself in GA operating in my current position of Client Manager/UAT Tester. Now I am interviewing for a QA Tester position, a field that I didn’t even know existed 5 years ago.

What I am confident of is that I will do my best in this role and have a wonderful career here with your team and your leadership. And when the time comes, I will assume a leadership role in order to aid this company in building its IT infrastructure.

17
Q

Why do want to work here?

A
  • Based on what I have heard so far, the company and I are sort of on the same journey as it relates to IT. You are venturing into unchartered territory because of the changing world that we live in because of this I see a lot of potential growth in the future for both of us.
18
Q

Why did you choose QA as a career?

A
  • It was actually interesting when I first heard about QA Testing, I thought to myself that this could not be true but it was. The person doing it was telling me about it. I’m choosing QA because it will allow me to service the customer in a different way from my client management role but still the same. Where they are similar is that I will still be advocating on the customer’s behalf, be it internal or external, by making sure I test their software as thoroughly as possible and help deliver to them a product that meets their expectation.
19
Q

How do you deal with a difficult person?

A
  • Well there was time when I had an idea how to improve the customer visibility to their data because the current way we were doing it was a little outdated and included information that were not relevant to the customer. I approached my team lead with this information and possible ways to improve it, to say the least, it was not well received. She shot it down and said there was nothing wrong with the current process. I waited a couple of days and invited her out to lunch and re-presented my idea but with more detail, stating how this would be of real benefit to the customer and how she would get the kudos for something initiated by her direct report. She saw my logic, apologized for the pervious outburst and gave me the go ahead. The customer really appreciated.
20
Q

What challenges have you encountered?

A
  • When Stericycle acquired another company and we had to merge our system with theirs and the goal was to integrate both applications to work as one on Salesforce. We are still in the process of it and are testing the two applications to make sure that they are working independently and still communicating with Salesforce. So basically we test everything from Smoke Test to UAT to make sure that the conversion is a smooth process. Through my experience as a UAT Tester testing this application, I’ve gained experience with conversion testing.
  • The challenges that we encountered initially was that most of the current employees were not strong in Salesforce so we had to get an external person to do some training on Salesforce and the advantage I had was that I had some background knowledge of Salesforce so I was able to support with the training and making sure that our team was able to come up to speed with it because we had timeframe to be able to test all the different applications including Salesforce. The challenging part was lack of the skill set from our team.
21
Q

End of Interview questions

A
  1. How much time do I have because I want to respect of your time?
  2. What should I expect next in the hiring process?
  3. Are there any reservations you have about my fit for this position that I can address for you before we finish the interview?
  4. If I were to start in this position today, what is the single biggest contribution I could make in the first few weeks?
  5. Let’s say in 6 months I’m really successful in this company, what does that look like to you?
22
Q

What is a Test Strategy?

A

A test strategy is high level view of how to approach the application, it’s written by the QA manager. It is not the same as the test plan.

23
Q

What is the SDLC (Software Development Life Cycle)?

A

SDLC (Software Development Life Cycle) is a process that ensures good software is built. It typically consists of 5 phases. Phase one starts with the requirement gathering led by the BA, Developer, PM and Tester Lead. Phase two is design, where the developers write how the application will be developed. The third is coding, where the developers code the application and Unit Test it. The fourth phase is the testing, where the testing team tests the application and enter defects/bugs when found and fifthly is the deployment/installation phase.

24
Q

What is the STLC (System Testing Life Cycle)?

A
STLC (System Testing Life Cycle) is the testing cycle during the testing phase of the SDLC for QA. It is a sequence of steps that are carried out in order to validate the software.  Its phases are:
•	Requirement Analysis
•	Test Planning
•	Test Case Development
•	Review of Test Cases
•	Test Execution
•	Bug logging and tracking 
•	Close and/or reopen bugs
25
Q

What are the Bug Report Component?

A

These are some of the components a bug report:
1. Short description of the problem or title

  1. Steps to reproduce
  2. Status, which is how the bug moves from person to person in the Bug Life Cycle
  3. Severity
  4. Priority
26
Q

What is a Bug Life Cycle?

A
  1. Bug found
  2. Bug reported
  3. Severity is assigned to the bug
  4. The bug is assigned to the developer who will fix it
  5. Tester reviews the bug to make sure it’s fixed and if it is closes it but if not re-opens it and the cycle begins afresh
27
Q

What is the bug?

A
  • The bug is a mismatch or discrepancy between the result specified in the Requirement and the actual behavior.
28
Q

What is a Test Plan?

A

A Test Plan is a document describing the scope, approach, resources, and schedule of intended testing activities.
It identifies test items, the features to be tested.

It includes:

  • Heading
  • Revision History
  • Table of Contents
  • Introduction
  • Scope
  • Approach
  • Overview
  • Types of testing
  • Types of software and hardware
  • Roles
  • Issues
  • Risks
  • Assumptions
  • Sign off section
29
Q

What document did you refer to write the Test Cases?

A

Requirement document, BRD in case of Waterfall or User Story in the case of Agile. (NOTE: It can also be Use Cases, or Design Document)

30
Q

What is Business Requirement Document (BRD)?

A

It is a document that describes in detail the functionalities that the user requires in the application. This document is written by the Business Analysts.

31
Q

What is the Waterfall methodology?

A

It is sequential design process. Where Development flows sequentially from start point to end point, with several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.

32
Q

What is the Agile methodology?

A

It is based on an incremental and iterative approach to software design. Allowing developers freedom to respond to changes in requirements as they arise. It is made up of scrum teams ; it’s carried out in sprints.

33
Q

What is a User Story?

A

A User Story is a short, simple description of a a feature told from the user’s/client’s prospective.

34
Q

What is the difference between Verification and Validation?

A
  • Verification ensures that the system (software, hardware, documentation, and personnel) complies with an organization’s standard and processes, relying on review or not-executable methods.
  • Validation physically ensures that the system operates according to plan by executing the system functions through a series of tests that can be observed and evaluated.

Verification answers the question, “Did we build the right system?” while validation addresses, “Did we build the system right?”

35
Q

Be ready for questions on how to test things other then software, like toaster, door knob, chairs anything.

A

The first question you need to ask is

  1. Do we have the requirement document?
  2. If there is non, ask to speak to the BA to get an understanding of what the user/client wants.
  3. If non, where’s the developer?
  4. Do positive testing first, give like 3 to 5.
  5. Do negative testing next, also give like 3 to 5.