Scribd
Upload
8 views

Day-3 assignment

Uploaded by

kanhuchpanda1997
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

Day-3 assignment

Uploaded by

kanhuchpanda1997
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Course Code

Course Name Fundamentals of Software Testing

Module 1 Day 3

Activity 1 Timing: 30 mins

1. Ask the participants to count (1, 2, 3...n). Two workgroups are formed – odd and even
numbers.
2. Ask participants to refer Activity 3.1: Test the Tester.
3. Ask the odd and even-numbered groups to refer to mobile phone and Iron box respectively.
4. Ask the participants to imagine that the products are set to be launched in the market. What
are the steps they would take to ensure that the products are ready to be sold? Which features
of the product would the testers test? Get the participants to discuss in their groups and note
their thoughts.

5. After the groups are done with the activity, they should present the testing process for their
specific products.

Activity 2 Timing: 20 mins

Ask each participant to imagine that they are working on a project "www.flipkart.com" as a test engineer
what are the roles and responsibilities they will have?

Activity 3 Timing: 30 mins

Scenarios Principle

The Marketing Manager of a well-known software


organization is demonstrating its newly developed mobile
phone in a public launch. In the middle of the demonstration
the Mobile phone suddenly crashes.
Do you think the company would not have tested their mobile
phone thoroughly?
Imagine testing a reservation system of Train Services.
Would it be practical to test all combinations of data?
40 origins and 40 destinations; 365 possible departure dates
(and return dates too), and 48 trains per day to choose from.
The parameters given above is a limited bit of data needed
when testing an airline system, but would these be enough to
raise your possible data combination?

Many problems in software systems can be traced back to a


missing or incorrect requirement. If the problem is not
detected and corrected in this stage, it can probably be found
during the Product Test stage, or in the User Acceptance
Test stage which may cause a lot of rework. Several work
products need to be corrected, and subsequently retested,
which may involve additional costs.

In the year 2005, a software company giant learned that 80


percent of the errors and crashes on their products were
caused by 20 percent of the bugs detected. More than 50
percent of the problem came from a mere one percent of all
flawed code.

The Test Suite of the Release 1 of a particular application


had a very high defect discovery rate per test case.
During an enhancement made to some modules of the
application, the same test suite was run without any updates.
From a high defect discovery rate, the test suite has detected
only a number of defects, which the testing team already
expected.

A banking system where financial transactions should work


accurately is tested in a different way from the website where
information can be viewed by everyone.

After Unit testing, no error is found for a particular module,


but this doesn’t mean that the software is defect-free and is
ready to be shipped.

Activity 4 Timing 30 mins

You are working on project of "www.Quikr.com” You are integrating online chat module to the website
for the account holder. Explain what are the activities involved in STLC.
Activity 5 Timing 30 mins

Form the team and assign some roles like

⮚ Project manager
⮚ Test Lead
⮚ Test Engineer
⮚ Business Analyst
⮚ Developer lead/manager
⮚ Developer

Ask them to discuss on stage their roles and responsibility they do in test planning.

You might also like