gadget.md

gistfile1.md

Product Selection:

Each student should select a product for testing. It can be any physical or digital product of their choice. Examples include mobile apps, websites, electronic gadgets, household appliances, or even a toy. Choose something that interests you and that you have access to for conducting tests effectively.

Test Objectives:

Define the objectives of your testing. Consider what aspects of the product you want to evaluate and what specific functionalities you want to test. Think about potential scenarios and edge cases that could arise during the product's usage.

Test Planning:

Before writing tests, create a test plan. Outline the different types of tests you will conduct, such as functional, usability, performance, security, or compatibility tests. Define the testing environment and tools you will need to execute your tests effectively.

Test Scenarios:

Identify a range of test scenarios to cover various aspects of the product. Consider both normal and abnormal situations that a user might encounter. Focus on edge cases, which are inputs or conditions that are outside the typical range and might cause unexpected behavior.

Test Cases:

Write individual test cases for each scenario identified in the previous step. A test case should include the following components:Test case name/identifier Description of the scenario being tested Preconditions (if any) Steps to reproduce the scenario

Expected results

Actual results (to be filled in after conducting the test) Edge Case Testing: Pay special attention to edge cases, as they often reveal unexpected issues. Identify specific edge cases for your selected product and design test cases to evaluate how the product handles such situations. Examples include testing extreme inputs, boundary values, or uncommon usage scenarios.

@noorin99, @HishamWattar. @jimaa-maya, mahmoudshahin

-The Product: NetFlix
-Test Objectives: Testing filtering and searching, testing payment.
-Test Planning: functional, testing tools: Jest Framework (Unit testing).
-Test Scenarios: Searching-- (If the input does not exist in the database). Payment--(Check if the default Credit or Debit card gets automatically added).
-Test Cases:

(If the input does not exist in the database):
describe('Search Database', () => {
test('Input does not exist in the database', () => {
// Arrange
const input = 'grape'; // Input that does not exist in the database

// Act
const result = searchDatabase(input);

// Assert
expect(result).toBe(false); // Expect the result to be false

});
});

---

(Check if the default Credit or Debit card gets automatically added):
describe('Payment', () => {
test('Default Credit or Debit card is automatically added', () => {
// Arrange
const paymentDetails = {
amount: 100,
cardNumber: '',
// Other payment details...
};

// Act
const result = makePayment(paymentDetails);

// Assert
expect(result).toBe('success'); // Expect the payment to be successful
expect(paymentDetails.cardNumber).toBe('1234567890'); // Expect the default card to be added

});
});

Expected results: The results of executing the function under the written conditions should pass the test, indicating that the function behaves correctly.

Room 12: @Younesnz @tarik310 @ilaydanurguzel1

Product: eBay

Test Objectives:

• if it's compatible with different browser and devices
• speed
• Performance
• Security
• Authentication
• Functionality
• user interface and experience

Test Planning:

Functional Testing:

• Searching
• content
• transactions
• placing bid

usability:

• user experience, user interface and being user friendly
• performance
• speed, website traffic under different network conditions

Security:

• Authentication, encryption and authorization

Compatibility

• with web browsers (Chrome Firefox and …) and operating systems (Android, IOS, …) and different screens

Test Scenarios:

Normal: user logs in, searches for a product, adds it to the card, searches for other products and add them to the card, proceeds to checkout
Abnormal: the user shouldn't have access to the routes.
Edge case: Ordering something which is out of stock

Test Cases

Normal:
Test Case Name: Purchase Flow
Description: Test from logging in to purchasing products, including search, add to card and transactions
Preconditions: the user should be signed up already
steps:
1- Authenticate the user with the database for logging in
2- searching for a product and the results
3- Add to card button and it successfully adds to the card
4- Adding more than 1 product to the card
5- Showing the payment page
6- validating shipping and card info
7- Review the order summary and confirm the purchase.

Expected Results: The product is successfully purchased, and the user receives a confirmation message.

Out of Time!