Technical Questions Flashcards
What is a bug?
A bug is any kind of error, mistake, or failure in the software code that prevents the software function from executing properly.
What is the difference between severity and priority?
These are important distinctions that must be known for proper time management. Severity is how difficult the issue is to fix. Priority is how important the issue is to fix.
Just because an issue is high severity doesn’t necessarily mean it’s high priority and vice-versa.
Here’s an example of a high-severity, low-priority issue:
The application crashes when a rarely used function is run on legacy software that most users can’t access.
Here’s an example of a low-severity, high-priority issue:
The wrong company logo is displayed on startup.
What is the difference between Assert and Verify commands in test automation?
There are a lot of similarities between the two commands. Both check if the code conditions are true. The difference is what happens next:
When an assert command fails, it will stop executing code, and the test will pause.
When a verify command fails, it will plow ahead and execute the rest of the code.
What is the difference between Quality Assurance, Quality Control, and Quality Testing?
Quality Assurance plans the way in which test process will be monitored within a team and organization. Quality Control finds defects and suggests ways to improve the software. Quality Testing is the process in which Quality Assurance and Quality Control find bugs.
When should QA start?
QA should begin as soon as possible. The earlier QA analysts, QA testers, and QA team leads get involved in the process, the more headaches are prevented later in the software development cycle. Static tests can be performed before the software is fully functional.
What is a test plan?
A test plan is a document that outlines the details of the intended test. It states the required roles, potential risk and solutions, and resources it will use before testing begins.
What does a test plan include?
Test plans should include:
- the scope
- the approach
- resources required
- intended schedule of the test(s)
What would you include in an automation test plan?
Since building a plan for automation testing is a big undertaking, you don’t have to go into every detail.
Instead, name a few important aspects of a test plan - for example, talk about how the plan should describe how the tests will be designed, how they will be executed, how defects will be managed, and what the test automation reporting will look like.
What is a Use Case?
Use Cases describe the cause and effect of a function. It makes sure that the user action and the system response are talking to each other properly.
What is a Test Strategy?
The test strategy outlines the plan for the testing stage of software development.
Unlike the test plan (which describes one specific test), the test strategy covers the entire testing phase of development and includes a description of the testing tools, test groups, test priorities, test record maintenance, and the test summary.
What are some different kinds of testing?
Regression testing, exploratory testing, functional testing, load testing, integration testing, unit testing, cross-browser testing, white box testing, black box testing, alpha testing, beta testing, and many more!
What do you think are some advantages of manual testing?
- Can be less expensive than automated testing
- For new teams or new people to QA, it can be easier to learn how to run a manual test so they can be rolled out faster
- Manual testing can be good for short-term projects when test scripts won’t be re-used many times
- You can analyze the product from the point of view of the end-user when doing manual testing
- Testing the GUI can feel more intuitive and lead to more accurate results when doing a manual test; the visual accessibility and preferences can be tricky to automate
What is a good test case?
A good test case clearly states the parameters in which the test will be performed and the bugs it hopes to find.
What is the difference between functional and nonfunctional testing?
Functional testing tests key parts of the software to ensure it matches requirements and specifications.
Nonfunctional testing tests are important but not crucial aspects of the software such as load times, stress, and overall performance.
When you find a bug in production, how do you ensure the bug gets resolved?
The best course of action is to immediately write a test case for the bug and run a regression test. That way, any future tests performed on the software should check specifically for that bug.
