Group 1

1. What is independent testing? Independent testing has many different levels, each level brings
different objectivity and effectiveness. Please clarify and give examples.
2. While there are many benefits to independent testing in a software development project, it's
important to note that this approach has potential drawbacks. You present some common
challenges associated with independent testing.
3. Three roles that are found within many test teams are those of the tester, test leader, and test
manager, you present the work done in these roles and define the skills test staff need.
4. While people tend to have different definitions of what goes in a test plan, for you, a test plan
is the project plan for the testing work to be done. Why do we write test plans? What types of
questions will you answer during test planning?
5. How to manage the test plan? According to you, which factors influence the test effort in
software testing?

Group 2

1. What is the difference between test plan, test strategy, and test approach in software testing?
2. Good project documentation is a positive factor, but do you think that the life cycle, time
pressure, the people factors also affect testing efforts? Please give your opinion and clarify.
3. Differentiate between two conceptually different estimation approaches: the metrics-based
approach and the expert-based approach. Take an example to clarify.
4. The purpose of configuration management in testing. Present and clarify problems caused by
poor configuration management. To support proper testing, configuration management may be
involved in ensuring what?
5. The projects do not always unfold as planned. Distinguish between the project and product
risks. Describe, using examples, how risk analysis and risk management may be used for test
planning.

Group 3

1. What is a bug log? Why log bugs? example.

2. What is a Bug Report/Defect Report?
3. There are many different things to include in your bug report, not all companies test the same
way. I think some content that you should write a report:
1) ID: Enter a unique number for the bug (for easy reference).
2) Module Name: Enter the name of the module in which the bug was discovered.
3) Release Version: Enter the version of the software in which the bug was detected.
4) Description/Summary: In addition to a clear title, add an easy-to-understand
description of the bug (e.g., “The invoice will not print for the user when they have the
invoice opened and click the Print button”).
5) Environment: Include any environment details (such as browser, operating system
[OS], URL, software version, etc.), so anyone reviewing the bug can easily glean the
environmental factors, and so development can replicate the bug and fix it.
6) Expected Result: How the software should have performed
8) Actual Result: How the software performed
 9) Screenshot: Add a screenshot of the bug, if applicable. That way, whatever the
software malfunctions, the issue will be clear to anyone reviewing the report.
10) Steps to Reproduce: Include the exact steps you take to reproduce the bug occurrence
11) Status: Specify the status of the bug using the Status dropdown list (e.g., new, open,
resolved, accepted, in progress, to be validated, done, etc.).
12) Bug Severity: Every bug must be assigned a level of severity and corresponding
priority. This reveals the extent to which the bug affects the system, and in turn, how
quickly it needs to be fixed.
13) Assignee: Enter the name of the employee who is responsible for ensuring that the
bug is fixed.
14) Reporter: Enter the name of the person who reported the bug.
15) Created: Enter the date that the bug was reported.
Please explain what the above contents are and let's example.
4. Benefits of a Bug Report?
5. What is the difference between severity and priority? example.
================================================================
Stopping to do Progress Test 2

==================================================================

Group 4

1. What is a test report? Why is a test report important?

2. What are the benefits of test reports in software testing?
3. Let's take an example of some test cases and use the following template to write a report
TEST CASE REPORT
(Use one template for each test case)

GENERAL INFORMATION

Test Stage: Unit Functionality Integration System Interface

Performance Regression Acceptance Pilot

Specify the testing stage for this test case.

Test Date: mm/dd/yy System Date, if mm/dd/yy

applicable:

Tester: Specify the name(s) of who is Test Case Number: Specify a unique test
testing this case scenario. number assigned to
the test case.

Test Case Provide a brief description of what functionality the case will test.
Description:
Results: Pass Fail Incident Number, if Specify the unique
applicable: identifier assigned to
the incident.

INTRODUCTION

Requirement(s) Identify the requirements to be tested and include the requirement number
to be tested:

Roles and Describe each project team member and stakeholder involved in the test, and identify
Responsibilities: their associated responsibility for ensuring the test is executed appropriately.

Set Up Describe the sequence of actions necessary to prepare for execution of the test.
Procedures:

Stop Describe the sequence of actions necessary to terminate the test.

Procedures:

ENVIRONMENTAL NEEDS

Hardware: Identify the qualities and configurations of the hardware required to execute the test
case.

Software: Identify system and application software required to execute the test case. Specify any
software that the test case will interact with.

Procedural Describe any constraints on the test procedures necessary to execute the test case.
Requirements:

TEST

Test Items and Identify and describe the items and features that will be exercised by the test case.
Features: Group the test cases into logically related scenarios that test related items and features.
For each item or feature, a reference to its associated requirement source should be
included.

Input Define each input required to execute the test case, and reference any required
Specifications: relationships between inputs.

Procedural Describe the sequences of actions necessary to prepare and execute the test case.
Steps: Provide detailed test procedures for each test case; explain precisely how each test
case will be executed.

Expected Describe the outcome anticipated from the test case. Specify the criteria to be used to
Results of Case: determine whether the item has passed or failed.
 ACTUAL RESULTS

Output Define all of the outputs and features required of the test case and provide expected
Specifications: values. While executing the test, record and describe the visually observable outputs as
they occur. Produce tangible evidence of the output such as a screen print. At the
conclusion, describe the actual outcome. Indicate whether the test passed or failed, and
identify any discrepancies between the expected results and the actual results.

4. What is the purpose of using the tool in testing activities? You can give examples to clarify the
tools being used for each testing phase/ business.
5. Potential benefits and risks of using tools. What advice do you have for special considerations
for types of tools?

Group 5

1. What is automation Testing? Advantages and disadvantages of automation testing? When

should you use the automation test?
2. Difference between manual test and automation test. Is manual testing easier than automation?
How do you decide which of the two works best for your business?
3. What is an example of automation testing? In your opinion, what knowledge is needed before
starting automation testing? explain more clearly
4. In your opinion, will dynamic testing replace manual testing in the future?
5. It is said that to do Testet you must have the following 6 soft skills:
a) Know how to ask the right questions, and when to ask
b) Know how to listen
c) Know how to focus on what business stakeholders care about... and forget the rest
d) Know how to manage time effectively
e) Know how to handle situations
f) Know how to trust your judgment - and intuition
Please clarify with examples and give your other views (if any).

Group 6
1. What is Agile Testing and why is it important?
2. The differences between working on traditional teams and working on agile teams. Roles and
activities on an Agile team
3. Some common roles and associated activities in an Agile team, characteristics, and
responsibilities of them
4. Clarify the following are the 12 principles and the four values of the Agile manifesto
5. Let's clarify 10 principles for Agile testers:
- Provide continuous feedback.
- Deliver value to the customer.
- Enable face-to-face communication.
- Have courage.
- Keep it simple.
- Practice continuous improvement.
- Respond to change.
 - Self-organize.
- Focus on people.
- Enjoy
Please give a real project example
6. Mostly used Agile Methods: scrum, Extreme Programming (XP), and Kaban. Present your
understanding of them and compare these methods