SOFTWARE TESTING MYTHS and FACTS

SOFTWARE TESTING MYTHS and FACTS

Just as every field has its myths, so does the field of Software Testing. Software testing myths have arisen primarily due to the following:

• Lack of authoritative facts.
• Evolving nature of the industry.
• General flaws in human logic.

Some of the myths are explained below, along with their related facts:

1. MYTH: Quality Control = Testing.
   • FACT: Testing is just one component of software quality control. Quality Control includes other activities such as Reviews.
2. MYTH: The objective of Testing is to ensure a 100% defect- free product.
   • FACT: The objective of testing is to uncover as many defects as possible while ensuring that the software meets the requirements. Identifying and getting rid of all defects is impossible.
3. MYTH: Testing is easy.
   • FACT: Testing can be difficult and challenging (sometimes, even more so than coding).
4. MYTH: Anyone can test.
   • FACT: Testing is a rigorous discipline and requires many kinds of skills.
5. MYTH: There is no creativity in testing.
   • FACT: Creativity can be applied when formulating test approaches, when designing tests, and even when executing tests.
6. MYTH: Automated testing eliminates the need for manual testing.
   • FACT: 100% test automation cannot be achieved. Manual Testing, to some level, is always necessary.
7. MYTH: When a defect slips, it is the fault of the Testers.
   • FACT: Quality is the responsibility of all members/ stakeholders, including developers, of a project.
8. MYTH: Software Testing does not offer opportunities for career growth.
   • FACT: Gone are the days when users had to accept whatever product was dished to them; no matter what the quality. With the abundance of competing software and increasingly demanding users, the need for software testers to ensure high quality will continue to grow.Software testing jobs are hot now.

Management folk tend to have a special affinity for myths and it will be your responsibility as a software tester to convince them that they are wrong. Put forward your arguments with relevant examples and numbers to validate your claims.

What is difference between Test Cases vs Test Scenario?

What is difference between Test Cases vs Test 

Scenario?

Test Case: A test case is a set of conditions or variables under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do.

Test Scenario: The exhaustive testing is not possible due to large number of data combinations and large number of possible paths in the software. Scenario testing is to make sure that end to end functionality of application under test is working as expected. Also check if the all business flows are working as expected. In scenario testing tester need to put his/her foot in the end users shoes to check and perform the action as how they are using application under test. In scenario testing the preparation of scenarios would be the most important part, to prepare the scenario tester needs to consult or take help from the client, stakeholder or developers

Difference between Test cases vs Test scenarios:

Test Case	Test Scenario
Test case consist of test case name, Precondition, steps / input condition, expected result.	Test scenario consists of a detailed test procedure. We can also say that a test scenario has many test cases associated with it. Before executing the test scenario we need to think of test cases for each scenario.
Test cases are low level actions and it can be derived from test scenarios.	Test scenarios are the high level classification of test requirement grouped depending on the functionality of a module and it can be derived from use cases.
Test case is give detailed information about if any pre-condition, what to test, how to test and expected result etc.	Test scenario is one liner statement which tell us about what to test.
Test case means detailed documenting the cases which help executing while testing.	Test Scenario means talking and thinking requirements in detail.
Test cases are set of steps which performed on system to verify the expected output.	Test scenario is thread of operations.
Test cases are more importance in case where development is happening onsite and QA is happening Off shored. It will help to understand and make both developer and QA in sync.	Test scenarios are more important when time to write test cases is no sufficient and team members are agree with the detailed one liner scenario.
Writing test cases is one time effort which can be used in future while executing regression test case. While reporting defects it will help tester to link the defect with test case id.	In new software testing generation it is new idea and time saver activity. The addition and modification (easy maintainability) of test scenarios is easy and independent on specific person.
The detailed test case document is full proof guard for new software tester. If developer missed something then it is easy to catch while executing these full-proof test cases.	One of the most positive point about test scenario is good test scenarios reduces the complexity and repeatability of product.
It requires more time and resources due to detailed test case which talks about how to test and what to test.	If the test scenario not detailed enough then it might take some time to discussion and understand what test scenario is exactly talking about.

 Here is quick example on how to write Test Cases vs Test Scenarios:

Example 1)

Requirement is to test your phone WiFi:

Test Scenario	Verify that device automatically connects to Wi-Fi if user creates new profile
Test cases	Test case 1: Create WiFi profile and verify that it created successfully
	Test case 2: Verify that device is able to connect to Wi-Fi

Example 2)

Sample Requirement: Use case ID: UC0001 – Verify and validate the end to end functionality of e-commerce website. Only register customers should be login into site using valid credentials and place the order.

Test Scenario:

[Click on the image to enlarge the image]

Test Cases:

User Test Cases: Unauthorized users should not be able to log on to Selenium Master ePortfolio

Unauthorized users should not be able to log on to Selenium Master ePortfolio

User story (Scenario):

Unauthorized users should not be able to log on to Selenium Master ePortfolio

Test Case

Step	Action	Expected Result	Test Data	Actual Result	Test Result	Note
1	Navigate to Selenium Master Test App URL: http://www.seleniummaster.com/seleniummastertestapp/index.php	Log in page displays
2	Enter username in the Username field.	Username should be entered and displayed in the username field	test
3	Enter wrong user password in the Password field.	Password should be entered in the password field	?????
4	Click on the Log in button.	Button should be clicked.
5	Verify that "Please check your username and password are correct" message is displayed.

User Test Cases :Users should be able to change password

Users should be able to change password

User story (Scenario):

User should be able to change password.

Test Case

Step	Action	Expected Result	Test Data	Actual Result	Test Result	Note
1	Navigate to Selenium Master Test App URL: http://www.facebook.com	Log in page displays
2	Click on the "Lost Username and Password" link	Username or password reset page should be displayed.
3	Enter email address or username in the text box field	Email address or username should be entered.
4	Click on the Send Request button	Button should be clicked.
5	Verify that password reset email notification message displayed.

User Test Cases:User should be able to change user settings

User should be able to change user settings

User story (Scenario):

Users should be able to change user settings.

Test Case

• Verify that users should be able to log on to the site. (see the corresponding log on test case)
• Verify that users should be able to change these account settings below:

• Password
• Username
• General account options
• Notifications
• Institution Membership

Step	Action	Expected Result	Test Data	Actual Result	Test Result	Note
1	Log on the site with valid username and password	Users should be able to log in the site.
2	Click on the "Settings" link on top of the page	My Account page should be displayed.
3	Check on the radio button "Nobody may add me as a friend"	Radio button "Nobody may me as a friend" should be checked.
4	Click on the "Save" button	Preference saved message should be displayed.

• Repeat the above steps for all options under General account options and verify that each change should be saved.
• Verify each options under Notification with the steps below.

Step	Action	Expected Result	Test Data	Actual Result	Test Result	Note
1	Log on the site with valid username and password	Users should be able to log in the site.
2	Click on the "Settings" link on top of the page	My Account page should be displayed.
3	Click on the Notification button	Notification settings change should be displayed.
4	Select "inbox" in the System message dropdown list box	"Inbox" option should be selected.
5	Click on the "Save" button	Preference saved message should be displayed.

• Repeat the above steps for all options under Notification options and verify that each change should be saved.

Test Scenarios as a user

As a user, in addition to log in to the site, change password and change user setting, a user should be able to perform following actions. Each action is a test scenario with various test steps (test steps are omitted here).

• User should be able to change profile.
• User should be able to change contact information.
• User should be able to change messaging.
• User should be able to change general information.
• User should be able to change user profile icon.
• User should be able to add resume.
• User should be able to upload files.
• User should be able to upload profile file.
• User should be able to create dashboard view.
• User should be able to create profile view.
• User should be able to copy a view.
• User should be able to find friends.
• User should be able to create groups.
• User should be able to join groups.
• User should be able to publish a blog.

Test Scenarios as an Admin

As an admin, in addition to log in to the site, change password and change admin user setting, an admin user should be able to perform following actions. Each action is a test scenario with various test steps (This is not a complete list. test steps are omitted here).

Add caption

• Admin should be able to change profile.
• Admin should be able to change contact information.
• Admin should be able to change messaging.
• Admin should be able to change general information.
• Admin should be able to change user profile icon.
• Admin should be able to add resume.
• Admin should be able to upload files.
• Admin should be able to upload profile file.
• Admin should be able to create dashboard view.
• Admin should be able to create profile view.
• Admin should be able to copy a view.
• Admin should be able to create groups.
• Admin should be able to publish a blog.
• Admin should be able to change site settings.
• Admin should be able to configure site.
• Admin should be able to manage users.
• Admin should be able to manage groups.
• Admin should be able to manage institutions.
• Admin should be able to manage site extensions.