100Days of Code Challenge

Diana_Farhat · 2025-01-13T00:11:02.757Z

Day 2: Writing Clean Code

I remember feeling proud after submitting a fully functional solution to an assignment I had worked hard to solve in my sophomore year, only to be surprised with disappointing feedback. My professor told me, ‘I don’t care if it works if I have to struggle to understand your spaghetti code.’

That moment stuck with me and taught me a powerful lesson: writing code isn’t just about making it functional—it’s about making it clear, maintainable, and readable.

Functional code solves a problem, but clean code solves it efficiently and allows others (and your future self) to understand and build upon it. Since then, I’ve committed myself to focus on clarity and simplicity, making sure my code reflects these principles:
• Readability: Write code that doesn’t require someone to “decode” your thought process.
• Consistency: Follow patterns and formatting rules, making the logic predictable.
• Documentation: Don’t leave others guessing—use clear comments and meaningful names for variables, functions, and classes.

This experience reminded me of a quote by Robert C. Martin (Uncle Bob):
“Clean code is simple and direct. Clean code reads like well-written prose.”

What I did today:
I revisited one of my older projects and refactored redundant, messy blocks of code into modular, reusable functions. The result? Simpler, cleaner, and more efficient.

My clean code checklist:
• Use meaningful names for variables, functions, and classes.
• Keep functions short and focused on a single task.
• Eliminate unnecessary comments—let your code be self-explanatory.
• Stick to consistent formatting and indentation.

Let’s raise the bar for quality! What are your go-to practices for writing clean code?
100daysofcode lebanon-mug

day21200×945 168 KB

Diana_Farhat · 2025-01-13T00:11:27.045Z

Day 1: Go GitHub Green

Starting your coding journey can be daunting at first, trying to learn it all at once.

When I first dove into coding, I was overwhelmed by the vastness of it all. The endless programming languages, frameworks, tools, and concepts felt like too much to grasp in one go. I remember sitting in front of my screen, looking at tutorials and thinking, “Where do I even start?” It felt like I was chasing a moving target, trying to catch it all at once.

But what I realized over time is that trying to build everything in one day is when I felt the most frustrated. I was pushing myself too hard, setting unrealistic goals for what I could achieve in such a short amount of time. The constant pressure to “get everything right” left me feeling stuck and disheartened.
Then something changed. I started focusing on the small steps—focusing on learning just one thing at a time. I set a goal to commit a small amount of code every day, no matter how insignificant it seemed. The biggest leaps came not when I tried to rush my progress, but when I embraced consistency. Slowly, I began to realize that every line of code, every small improvement, was building the foundation of something bigger.

You may feel like you’re barely improving day by day, but fast forward a year, and you’d see how everything ties together. All those small wins, those tiny green squares on GitHub, they add up.

So trust the process, stay consistent, and keep those squares green

github1920×347 13.2 KB

100daysofcode lebanon-mug

Diana_Farhat · 2025-01-13T00:11:31.963Z

Hello community!

I’ve been challenged to start the #100DayCodeChallenge, and guess what?! Challenge Accepted!! So for the next 100 days, I’ll be sharing my knowledge, learning, and experiences.

Below is my progress from previous days, and I’ll now be updating regularly from today. If you’re up for it, join me on this adventure!

image1035×582 71.5 KB

100daysofcode lebanon-mug

Nisrine_bg · 2025-01-13T18:50:34.767Z

Day 4 of 100daysofcode : Mastering Selenium Locators

Locators in Selenium are used to identify and interact with web elements on a webpage, such as buttons, input fields, or links. They enable automated scripts to perform actions like clicking, typing, or retrieving information, making them essential for effective web automation.

Here’s a list of all the locators used in Selenium:

ID
Name
Class Name
Tag Name
Link Text
Partial Link Text
CSS Selector
XPath
DOM Locator (via JavaScript execution)

These locators provide a variety of ways to identify and interact with web elements depending on the structure of the webpage.

100daysofcode lebanon-mug
locators

Nisrine_bg · 2025-01-14T21:41:02.849Z

Day 5 of 100daysofcode : So, how do locators really work using Selenium?

Locators in Selenium work by identifying elements on a webpage using their unique attributes or properties, such as id, name, class, or tag structure.

Selenium communicates with the browser’s DOM (Document Object Model) to search for elements that match the specified locator. Once an element is located, Selenium enables interactions like clicking, typing, or extracting data.

By combining locators with Selenium’s powerful methods, testers can precisely target elements even on dynamic and complex web pages.

1. ID Locator

Description: Uses the id attribute of an HTML element.
Syntax:

element = driver.find_element(By.ID, "element_id")

Advantages:
- Unique within a page.
- Fast and reliable.

2. Name Locator

Description: Uses the name attribute of an HTML element.
Syntax:

element = driver.find_element(By.NAME, "element_name")

Advantages:
- Simple and effective if name attributes are unique.
Disadvantages:
- May not always be unique.

3. Class Name Locator

Description: Uses the class attribute of an HTML element.
Syntax:

element = driver.find_element(By.CLASS_NAME, "class_name")

Advantages:
- Works well for elements with specific styling.
Disadvantages:
- Fails when multiple elements share the same class.

4. Tag Name Locator

Description: Uses the HTML tag name (e.g., input, button).
Syntax:

element = driver.find_element(By.TAG_NAME, "tag_name")

Use Case:
- Retrieving collections of elements like all links (<a> tags) on a page.

5. Link Text Locator

Description: Locates links based on their text.
Syntax:

element = driver.find_element(By.LINK_TEXT, "Link Text")

Use Case:
- Ideal for links with unique text.
Disadvantages:
- May not work well with long or dynamic text.

6. Partial Link Text Locator

Description: Locates links using partial text match.
Syntax:

element = driver.find_element(By.PARTIAL_LINK_TEXT, "Partial Text")

Use Case:
- Useful when link text is too long or dynamic.

7. CSS Selector

Description: Uses CSS selectors to locate elements.
Syntax:

element = driver.find_element(By.CSS_SELECTOR, "css_selector")

Advantages:
- Extremely flexible and powerful.
- Supports complex matching patterns.
Examples:
- By class: ".classname"
- By ID: "#id"
- By attribute: [type='submit']

Locators in Selenium are used to identify web elements on a webpage. They are a fundamental part of Selenium’s interaction with web applications. Here’s a detailed overview of the commonly used locators in Selenium:

from selenium import webdriver
from selenium.webdriver.common.by import By

# Initialize the WebDriver
driver = webdriver.Chrome()

# Open the practice login page
driver.get("https://practicetestautomation.com/practice-test-login/")

# Locate the username and password fields
username_field = driver.find_element(By.ID, "username")
password_field = driver.find_element(By.ID, "password")

# Enter credentials
username_field.send_keys("student")
password_field.send_keys("Password123")

# Locate and click the login button using a CSS Selector
login_button = driver.find_element(By.CSS_SELECTOR, "button[type='submit']")
login_button.click()

# Validate login by checking the URL or a success message
success_message = driver.find_element(By.TAG_NAME, "h1")
assert success_message.text == "Logged In Successfully", "Login failed!"

# Close the browser
driver.quit()

Nisrine_bg · 2025-01-15T21:59:48.246Z

Day 6 of 100daysofcode : Testing Interactive Elements using Selenium

To test all the interactive elements on the DemoQA website using Selenium, we need to cover different types of elements such as:

Checkboxes
Radio Buttons
Text Inputs
Buttons
Links
Alerts
Sliders
Forms

Below is an example Selenium script that tests all major elements on the DemoQA website

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.common.keys import Keys
from selenium.webdriver.common.action_chains import ActionChains
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
import time

# Initialize WebDriver (Chrome in this example)
options = webdriver.ChromeOptions()
options.add_argument('--start-maximized')
driver = webdriver.Chrome(options=options)

# Function to test all elements on the DemoQA website
def test_demoqa_elements():
    driver.get("https://demoqa.com/")
    
    # Wait for the page to load
    WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.TAG_NAME, "body")))
    
    # Test Checkboxes
    print("Testing Checkboxes...")
    driver.find_element(By.XPATH, "//span[text()='Elements']").click()
    WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.XPATH, "//span[text()='Checkbox']"))).click()
    
    checkbox1 = driver.find_element(By.CLASS_NAME, "rct-checkbox")
    checkbox1.click()
    time.sleep(1)
    print("Checkbox selected.")
    
    checkbox1.click()  # Deselecting
    print("Checkbox deselected.")
    
    # Test Radio Buttons
    print("Testing Radio Buttons...")
    driver.find_element(By.XPATH, "//span[text()='Radio Button']").click()
    WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.XPATH, "//label[text()='Yes']"))).click()
    time.sleep(1)
    print("Radio Button 'Yes' selected.")
    
    # Test Text Inputs
    print("Testing Text Inputs...")
    driver.find_element(By.XPATH, "//span[text()='Text Box']").click()
    WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.ID, "userName"))).send_keys("John Doe")
    driver.find_element(By.ID, "userEmail").send_keys("john.doe@example.com")
    driver.find_element(By.ID, "currentAddress").send_keys("123 Main St.")
    driver.find_element(By.ID, "permanentAddress").send_keys("456 Oak St.")
    driver.find_element(By.XPATH, "//button[text()='Submit']").click()
    time.sleep(1)
    print("Text box form submitted.")
    
    # Test Buttons
    print("Testing Buttons...")
    driver.find_element(By.XPATH, "//span[text()='Buttons']").click()
    WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.ID, "doubleClickBtn"))).click()
    time.sleep(1)
    print("Button clicked.")
    
    # Test Links
    print("Testing Links...")
    driver.find_element(By.XPATH, "//span[text()='Links']").click()
    WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.XPATH, "//a[text()='Home']"))).click()
    print("Navigated to 'Home' link.")
    time.sleep(2)
    
    # Test Alerts
    print("Testing Alerts...")
    driver.find_element(By.XPATH, "//span[text()='Alerts, Frame & Windows']").click()
    driver.find_element(By.ID, "alertButton").click()
    WebDriverWait(driver, 10).until(EC.alert_is_present())
    driver.switch_to.alert.accept()  # Accept the alert
    print("Alert accepted.")
    
    # Test Sliders
    print("Testing Sliders...")
    driver.find_element(By.XPATH, "//span[text()='Slider']").click()
    slider = driver.find_element(By.XPATH, "//input[@type='range']")
    ActionChains(driver).drag_and_drop_by_offset(slider, 50, 0).perform()  # Move slider
    time.sleep(1)
    print("Slider value changed.")
    
    # Test Modal Dialog
    print("Testing Modal Dialog...")
    driver.find_element(By.XPATH, "//span[text()='Modal Dialogs']").click()
    driver.find_element(By.ID, "showSmallModal").click()  # Open small modal
    WebDriverWait(driver, 10).until(EC.presence_of_element_located((By.ID, "closeSmallModal"))).click()  # Close modal
    print("Modal dialog tested.")
    
    # Test Accordions
    print("Testing Accordions...")
    driver.find_element(By.XPATH, "//span[text()='Accordions']").click()
    driver.find_element(By.XPATH, "//button[text()='First Button']").click()  # Expand first section
    time.sleep(1)
    print("Accordion section expanded.")
    
# Run the test function
try:
    test_demoqa_elements()
finally:
    driver.quit()

Nisrine_bg · 2025-01-16T21:29:47.538Z

Day 7: Find The Bug

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.common.keys import Keys
import time

# Set up the WebDriver
driver = webdriver.Chrome()

try:
    # Open the website
    driver.get("https://the-internet.herokuapp.com/login")

    # Locate the username field and enter text
    username_field = driver.find_element(By.ID, "username")
    username_field.send_keys("tomsmith")  # Correct username

    # Locate the password field and enter text
    password_field = driver.find_element(By.ID, "password")
    password_field.send_keys("SuperSecretPassword!")  # Correct password

    # Click the login button
    login_button = driver.find_element(By.XPATH, "//button[@type='submit']")
    login_button.click()

    # Wait for a short while to allow the page to load
    time.sleep(3)

    # Verify if the login was successful by checking for a specific element
    success_message = driver.find_element(By.XPATH, "//div[@class='flash success']")
    assert "You logged into a secure area!" in success_message.text
    print("Test Passed: Login successful!")

    #Click the logout button
    logout_button = driver.find_element(By.CLASS_NAME, "icon-2x icon-signout")
    logout_button.click()

except AssertionError as e:
    print("Test Failed: Assertion error -", e)
except Exception as e:
    print("Test Failed: An error occurred -", e)
finally:
    # Close the browser
    driver.quit()

Nisrine_bg · 2025-01-17T18:45:25.382Z

Day 8 of 100daysofcode : Essential Selenium skills every QA Engineer must know

𝟭. 𝗖𝗼𝗿𝗲 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀
Open-source web automation framework.
Components: WebDriver, IDE, Grid.

𝟮. 𝗦𝗲𝘁𝘂𝗽
Install required language (Java, Python).
Configure IDE and WebDriver.

𝟯. 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲
Proficiency in Java, Python, C#, etc.

𝟰. 𝗟𝗼𝗰𝗮𝘁𝗼𝗿𝘀
Identify web elements: ID, CSS, XPath, etc.

𝟱. 𝗪𝗲𝗯𝗗𝗿𝗶𝘃𝗲𝗿 𝗕𝗮𝘀𝗶𝗰𝘀
Browser actions: Click, Send Keys, Navigation.
Handle iframes, alerts, and pop-ups.

𝟲. 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗧𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀
Waits (Implicit, Explicit, Fluent).
Switch windows, manage cookies, take screenshots.

𝟳. 𝗧𝗲𝘀𝘁 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀
Integrate with JUnit, TestNG, or PyTest.
Data-driven testing and test suites.

𝟴. 𝗣𝗮𝗿𝗮𝗹𝗹𝗲𝗹 𝗧𝗲𝘀𝘁𝗶𝗻𝗴
Use Selenium Grid for distributed execution.

𝟵. 𝗕𝗲𝘀𝘁 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀
Reusable scripts, Page Object Model (POM).

𝟭𝟬. 𝗖𝗜/𝗖𝗗 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻
Use Jenkins, GitHub Actions, etc., for automation pipelines.

𝟭𝟭. 𝗥𝗲𝗽𝗼𝗿𝘁𝗶𝗻𝗴

Tools: Extent, Allure.
Logging: Log4j, Python logging.

𝟭𝟮. 𝗗𝘆𝗻𝗮𝗺𝗶𝗰 𝗖𝗼𝗻𝘁𝗲𝗻𝘁

Sync with dynamic elements, use JavaScript Executor.

𝟭𝟯. 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴

IDE tools, browser developer tools, handle exceptions.

𝟭𝟰. 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻

Avoid Thread.sleep(), optimize waits and locators.

𝟭𝟱. 𝗔𝗣𝗜 𝗧𝗲𝘀𝘁𝗶𝗻𝗴

Combine Selenium with Postman or RestAssured.

DALL·E 2025-01-17 19.35.03 - A futuristic and professional-themed illustration showcasing Selenium automation testing for QA Engineers. The image includes a browser window with co1024×1024 556 KB

100daysofcode lebanon-mug

Nisrine_bg · 2025-01-18T21:22:20.859Z

Day 9 of 100daysofcode : Top Challenges QA Engineers Face with Selenium—and How to Overcome Them

𝟭. 𝗦𝘁𝗲𝗲𝗽 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗖𝘂𝗿𝘃𝗲

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Beginners may find it difficult to grasp Selenium due to its reliance on programming languages like Java, Python, or C#.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Focus on learning the basics of the programming language first and gradually build Selenium skills.

𝟮. 𝗛𝗮𝗻𝗱𝗹𝗶𝗻𝗴 𝗗𝘆𝗻𝗮𝗺𝗶𝗰 𝗘𝗹𝗲𝗺𝗲𝗻𝘁𝘀

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Many modern web applications use dynamic IDs or elements that change with each session, making it hard to locate elements reliably.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use robust locators like XPath, CSS selectors, or unique attributes.

𝟯. 𝗖𝗿𝗼𝘀𝘀-𝗕𝗿𝗼𝘄𝘀𝗲𝗿 𝗧𝗲𝘀𝘁𝗶𝗻𝗴

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Ensuring compatibility across different browsers can lead to inconsistencies due to varying browser implementations.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use the WebDriver API and run extensive testing across all required browsers.

𝟰. 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝗮𝗻𝗱 𝗧𝗲𝘀𝘁 𝗙𝗹𝗮𝗸𝗶𝗻𝗲𝘀𝘀

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Tests can fail intermittently due to issues like timing, network latency, or improper waits.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Implement explicit or fluent waits instead of implicit waits and ensure proper synchronization.

𝟱. 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝗢𝘁𝗵𝗲𝗿 𝗧𝗼𝗼𝗹𝘀

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Integrating Selenium with CI/CD pipelines, reporting tools, or test management platforms can be complex.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use frameworks like TestNG, JUnit, or integrations with Jenkins, GitHub Actions, or other tools.

𝟲. 𝗟𝗶𝗺𝗶𝘁𝗲𝗱 𝗦𝘂𝗽𝗽𝗼𝗿𝘁 𝗳𝗼𝗿 𝗖𝗮𝗽𝘁𝗰𝗵𝗮𝘀 𝗮𝗻𝗱 𝗧𝘄𝗼-𝗙𝗮𝗰𝘁𝗼𝗿 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Automating tests involving captchas or 2FA is not straightforward.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use test environments with disabled captchas or simulate user behavior with backend support.

𝟳. 𝗛𝗮𝗻𝗱𝗹𝗶𝗻𝗴 𝗣𝗼𝗽-𝗨𝗽𝘀 𝗮𝗻𝗱 𝗔𝗹𝗲𝗿𝘁𝘀

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Pop-ups, alerts, or authentication windows may not be handled seamlessly by Selenium.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use Selenium’s switchTo() methods or consider custom scripts for better handling.

𝟴. 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 𝗠𝗼𝗯𝗶𝗹𝗲 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Selenium does not natively support mobile testing; you need tools like Appium for mobile platforms.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Integrate Selenium with Appium or use other mobile testing tools.

𝟵. 𝗟𝗮𝗰𝗸 𝗼𝗳 𝗕𝘂𝗶𝗹𝘁-𝗶𝗻 𝗥𝗲𝗽𝗼𝗿𝘁𝗶𝗻𝗴

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Selenium does not provide detailed reporting features.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use third-party libraries or frameworks such as Extent Reports, Allure, or TestNG reports.

𝟭𝟬. 𝗠𝗮𝗶𝗻𝘁𝗮𝗶𝗻𝗶𝗻𝗴 𝗧𝗲𝘀𝘁 𝗦𝗰𝗿𝗶𝗽𝘁𝘀

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: As applications evolve, maintaining Selenium test scripts becomes time-consuming.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Follow modular frameworks, use Page Object Model (POM), and keep scripts well-documented.

𝟭𝟭. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗮𝗻𝗱 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗜𝘀𝘀𝘂𝗲𝘀

𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲: Running extensive test suites can be time-consuming and resource-intensive.
𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Use grid-based execution like Selenium Grid or cloud-based solutions like BrowserStack or Sauce Labs.

100daysofcode lebanon-mug

Nisrine_bg · 2025-01-19T20:47:55.740Z

Day 10: Introduction to Cypress: A Modern End-to-End Testing Framework

Cypress is a modern, open-source JavaScript-based testing framework designed for end-to-end testing of web applications.
It provides a fast, reliable, and easy-to-use environment for writing, debugging, and running tests directly in the browser. Developers use Cypress to verify user flows, UI components, and application functionality across different browsers, ensuring a seamless user experience.

1_4_A4csvTUNJzriWeNFC54w770×207 106 KB

100daysofcode lebanon-mug

Nisrine_bg · 2025-01-20T21:11:17.838Z

Day 11:### 10 Things You Need to Know About Using Cypress in Testing

Built for Modern Web: Cypress thrives on real-time reloading for dynamic apps.
Fast and Flawless Debugging: Time-travel your tests with snapshots of every step.
No Selenium Here: It’s an independent powerhouse, running directly in the browser.
Built-in Waiting: Forget sleep(). Cypress automatically waits for elements.
Rich Error Messages: It doesn’t just fail—it tells you why with detailed logs.
All-in-One: Test runner, assertions, and stubbing, all in one tool.
JavaScript Rules: Your tests are written in JavaScript for maximum flexibility.
Mocks Made Easy: Seamlessly stub or mock APIs to control test environments.
Cross-Browser Testing: From Chrome to Firefox, Cypress has your back.
Perfect for CI/CD: Integrate easily with Jenkins, CircleCI, and others.

Nisrine_bg · 2025-01-21T21:38:10.909Z

Day 12 of 100daysofcode : Top 5 scenarios where Cypress is most effective

1. End-to-End Testing

Cypress is primarily designed for E2E testing of web applications. Use it to test the complete workflow of an application, from the user interface to backend interactions.
Example: Testing a login process, form submission, or multi-step checkout process.

2. UI/UX Testing

Cypress excels at testing the user interface and ensuring elements are displayed correctly and behave as expected.
Example: Verifying that buttons, menus, modals, and animations work as intended.

3. Integration Testing

It is suitable for testing how different parts of your application interact with each other, especially in single-page applications.
Example: Checking that API responses update the UI as expected or that dependent components render correctly.

4. Cross-Browser Testing

Cypress supports multiple browsers like Chrome, Edge, and Firefox, making it a good choice for cross-browser compatibility testing.
Example: Ensuring that the application behaves consistently across supported browsers.

5. Continuous Integration/Delivery Pipelines

Cypress integrates seamlessly with CI/CD tools (like Jenkins, GitHub Actions, and GitLab CI) for automated testing during deployment.
Example: Running test suites on every code push or before a production release to catch regressions early.

DALL·E 2025-01-21 23.35.53 - A vibrant, modern illustration showcasing the diverse use cases of Cypress for testing in software development. The image features multiple connected1792×1024 612 KB

Nisrine_bg · 2025-01-22T20:04:39.250Z

Day 13 of 100daysofcode : Here are 10 tips and tricks to effectively use Cypress for automation testing:

1. Use Custom Commands

Simplify repetitive tasks by defining custom commands in the cypress/support/commands.js file.

Example:

Cypress.Commands.add('login', (username, password) => {
  cy.visit('/login');
  cy.get('#username').type(username);
  cy.get('#password').type(password);
  cy.get('#submit').click();
});

This keeps your test cases clean and reusable.

2. Leverage Cypress Fixtures

Use the fixtures folder to store reusable test data in JSON files.

Example:

cy.fixture('user').then((user) => {
  cy.get('#username').type(user.username);
  cy.get('#password').type(user.password);
});

3. Take Advantage of Assertions

Cypress has built-in assertions that simplify verifying UI elements.

Example:

cy.get('.alert').should('be.visible').and('contain', 'Success');

4. Use Cypress Selectors Carefully

Use data-* attributes for stable selectors instead of classes or IDs that may change.

Example:

<button data-cy="submit-btn">Submit</button>

cy.get('[data-cy=submit-btn]').click();

5. Handle Network Requests with `cy.intercept`

Mock API requests and responses to test edge cases or scenarios.

Example:

cy.intercept('GET', '/api/users', { fixture: 'users.json' }).as('getUsers');
cy.visit('/users');
cy.wait('@getUsers');

6. Utilize Cypress Plugins

Extend functionality using Cypress plugins like cypress-axe for accessibility testing or cypress-file-upload for file uploads.

Example with cypress-file-upload:

cy.get('input[type="file"]').attachFile('file-to-upload.pdf');

7. Use `.then()` for Synchronous Commands

Chain asynchronous Cypress commands for cleaner test flows.

Example:

cy.get('#price').invoke('text').then((priceText) => {
  const price = parseFloat(priceText);
  expect(price).to.be.greaterThan(0);
});

8. Take Screenshots and Videos

Use cy.screenshot() for debugging or visual regression testing.
Enable video recording in the cypress.config.js file for CI/CD environments.

9. Parallelize Tests for Speed

Leverage Cypress Dashboard to split test execution across multiple machines or threads.
Example: Use the --parallel flag:
```
npx cypress run --record --parallel
```

10. Debugging with Cypress

Use cy.pause() to pause tests at specific steps.
Use .debug() to inspect elements in the browser.
Leverage the built-in Cypress debugger with the browser’s Developer Tools.

By incorporating these tips into your Cypress workflow, you can write more efficient, maintainable, and robust automated tests.

lebanon-mug

Nisrine_bg · 2025-01-23T21:09:31.583Z

Day 14 of 100daysofcode : Cypress Setup

Setting up Cypress for automation testing is straightforward and involves a few steps. Below is a detailed guide:

Step 1: Install Node.js

Cypress requires Node.js to run. If you don’t have Node.js installed:

Download it from Node.js official website.
Install it by following the prompts.

Step 2: Create a Project Directory

Open your terminal or command prompt.
Create a new project folder for your automation tests:
```
mkdir cypress-automation
cd cypress-automation
```
Initialize a new Node.js project:
```
npm init -y
```
This creates a package.json file to manage your project dependencies.

Step 3: Install Cypress

Run the following command to install Cypress:

npm install cypress --save-dev

This will add Cypress as a development dependency in your project.

Step 4: Open Cypress

After installation, you can open Cypress using the following command:

npx cypress open

This command will:

Launch the Cypress Test Runner.
Create a default folder structure (cypress/) in your project directory:
- cypress/e2e: Place your test files here.
- cypress/fixtures: Store static data (e.g., JSON files) for your tests.
- cypress/support: Add custom commands or reusable logic here.

Step 5: Write Your First Test

Inside the cypress/e2e folder, create a new test file, for example:
```
touch cypress/e2e/sample_test.cy.js
```

Add a simple test in the file:

describe('My First Test', () => {
  it('Visits the Cypress website', () => {
    cy.visit('https://www.cypress.io');
    cy.contains('Features').click();
    cy.url().should('include', '/features');
  });
});

Step 6: Run Tests

Start Cypress Test Runner:
```
npx cypress open
```
Select the test file you created (sample_test.cy.js) and run it.

Step 7: Configure Cypress (Optional)

You can customize Cypress settings in the cypress.config.js or cypress.config.ts file created in your project root. For example, to set a base URL for your tests:

const { defineConfig } = require('cypress');

module.exports = defineConfig({
  e2e: {
    baseUrl: 'https://example.com',
    setupNodeEvents(on, config) {
      // implement node event listeners here
    },
  },
});

Step 8: Add Cypress to Scripts (Optional)

To make running tests easier, add Cypress commands to your package.json scripts:

"scripts": {
  "cypress:open": "cypress open",
  "cypress:run": "cypress run"
}

Now, you can run Cypress with:

npm run cypress:open: Opens the Test Runner.
npm run cypress:run: Runs tests in headless mode.

Step 9: Integrate Cypress with CI/CD (Optional)

To run Cypress tests in CI/CD pipelines, you can use the cypress run command. Add this step to your CI/CD configuration file (e.g., GitHub Actions, Jenkins, or CircleCI).

Step 10: Explore More Features

Assertions: Use Chai.js assertions built into Cypress.
Fixtures: Load external test data using cy.fixture().
Custom Commands: Add reusable logic in cypress/support/commands.js.

For more details, visit the Cypress Documentation.

lebanon-mug

Nisrine_bg · 2025-01-24T19:03:39.081Z

Day 15 of 100daysofcode : Cypress Test for Login Functionality

describe('Login Page Test', () => {
  it('should allow a user to log in successfully', () => {
    // Visit the login page
    cy.visit('https://example.com/login');

    // Enter username and password
    cy.get('input[name="username"]').type('testuser');
    cy.get('input[name="password"]').type('Password123');

    // Click the login button
    cy.get('button[type="submit"]').click();

    // Assert the user is redirected to the dashboard
    cy.url().should('include', '/dashboard');
    
    // Assert the welcome message is displayed
    cy.contains('Welcome, Test User!').should('be.visible');
  });
});

Key Points:

cy.visit(): Navigates to the specified URL.
cy.get(): Finds elements using CSS selectors.
type(): Types text into an input field.
click(): Clicks on a button or element.
Assertions:
- should('include') verifies the URL.
- should('be.visible') confirms an element is visible.

This example assumes that the login page contains inputs with the names username and password and a button with type="submit". You can adapt the selectors and assertions based on your application.

lebanon-mug

Nisrine_bg · 2025-01-26T08:41:17.211Z

Day 16 of 100daysofcode : Testing Websites using Cypress

describe(‘Login Automation Test’, () => {
const baseUrl = ‘https://the-internet.herokuapp.com’;

beforeEach(() => {
// Visit the base URL before each test
cy.visit(${baseUrl}/login);
});

it(‘should login successfully with valid credentials’, () => {
cy.get(‘#username’).type(‘tomsmith’); // Enter valid username
cy.get(‘#password’).type(‘SuperSecretPassword!’); // Enter valid password
cy.get(‘button[type=“submit”]’).click(); // Click the Login button

// Assert successful login
cy.get('.flash.success').should('contain.text', 'You logged into a secure area!');

});

it(‘should show error for invalid credentials’, () => {
cy.get(‘#username’).type(‘invalidUser’); // Enter invalid username
cy.get(‘#password’).type(‘invalidPassword’); // Enter invalid password
cy.get(‘button[type=“submit”]’).click(); // Click the Login button

// Assert error message
cy.get('.flash.error').should('contain.text', 'Your username is invalid!');

});
});
lebanon-mug

Nisrine_bg · 2025-01-26T21:20:30.702Z

Day 17 of 100daysofcode : Cypress Test Code for Wikipedia Search Functionality

describe('Wikipedia Search Functionality Test', () => {
  before(() => {
    // Visit Wikipedia homepage before the tests
    cy.visit('https://www.wikipedia.org');
  });

  it('should display the search input and language selector', () => {
    // Check if the search input is visible
    cy.get('input#searchInput').should('be.visible');

    // Check if the language selector dropdown is visible
    cy.get('select#searchLanguage').should('be.visible');
  });

  it('should successfully perform a search and display

Nisrine_bg · 2025-01-27T20:57:00.804Z

Day 18 of 100daysofcode : Advanced Automation using Cypress

Here’s an advanced automation testing script using Cypress. The script tests key functionalities of a sample e-commerce website, such as logging in, searching for a product, adding it to the cart, and completing a checkout process.

Prerequisites

Ensure you have Cypress installed and set up. Run the following in your project folder:

npm install cypress --save-dev

Cypress Script

// cypress/e2e/ecommerce_advanced_test.cy.js

describe('E-Commerce Website - Advanced Automation Test', () => {
  const baseUrl = 'https://example-ecommerce.com'; // Replace with the actual website URL

  before(() => {
    cy.visit(baseUrl); // Navigate to the website
  });

  it('Logs in successfully', () => {
    cy.get('a[href="/login"]').click(); // Click on the Login link
    cy.get('input[name="email"]').type('testuser@example.com'); // Enter email
    cy.get('input[name="password"]').type('TestPassword123!'); // Enter password
    cy.get('button[type="submit"]').click(); // Submit login form

    // Assert successful login
    cy.get('.user-profile').should('contain', 'Welcome, Test User'); 
  });

  it('Searches for a product and adds it to the cart', () => {
    cy.get('input[placeholder="Search"]').type('Wireless Mouse{enter}'); // Search for a product
    cy.get('.product-list').should('contain', 'Wireless Mouse'); // Assert product appears

    // Select the product
    cy.get('.product-card').contains('Wireless Mouse').click();

    // Add the product to the cart
    cy.get('button').contains('Add to Cart').click();

    // Assert product is added to the cart
    cy.get('.cart-notification').should('contain', 'Wireless Mouse added to your cart');
  });

  it('Completes the checkout process', () => {
    cy.get('.cart-icon').click(); // Open the cart
    cy.get('button').contains('Proceed to Checkout').click(); // Proceed to checkout

    // Fill in shipping information
    cy.get('input[name="address"]').type('123 Cypress St, Test City, TX');
    cy.get('input[name="zip"]').type('12345');
    cy.get('input[name="phone"]').type('1234567890');

    // Choose payment method and complete the payment
    cy.get('input[name="payment"][value="credit-card"]').check();
    cy.get('input[name="card-number"]').type('4111111111111111');
    cy.get('input[name="expiry"]').type('12/25');
    cy.get('input[name="cvv"]').type('123');
    cy.get('button').contains('Place Order').click();

    // Assert order completion
    cy.get('.order-confirmation').should('contain', 'Thank you for your order');
  });

  after(() => {
    // Log out after tests
    cy.get('.user-menu').click();
    cy.get('a').contains('Logout').click();

    // Assert successful logout
    cy.get('a[href="/login"]').should('be.visible');
  });
});

Key Features of the Script:

Modularized Tests: Each test case handles a specific functionality, making the script easier to debug and maintain.
Dynamic Selectors: Uses robust and descriptive selectors to ensure test stability.
Assertions: Verifies that each step is successful with should() assertions.
Reusable Code: Leverages Cypress commands like cy.get() and chaining for efficiency.
Complete Flow: Covers login, search, cart, checkout, and logout processes.

Run the Test

To execute the test, run the following command:

npx cypress open

From the Cypress Test Runner, select the ecommerce_advanced_test.cy.js file to run the test.
lebanon-mug

Nisrine_bg · 2025-01-28T20:01:40.071Z

Day 19 of 100daysofcode : Playwright - For cross-browser end-to-end testing

Playwright is an excellent tool for cross-browser end-to-end testing. Developed by Microsoft, it provides fast and reliable automation for testing web applications across modern browsers. Here’s an overview of what makes Playwright stand out:

Key Features of Playwright

Cross-Browser Support:

Works seamlessly with Chromium (Google Chrome, Microsoft Edge), WebKit (Safari), and Firefox.
Ensures your application is functional across all major browsers.

Headless and Headed Modes:

Tests can be run in headless mode for faster execution or in headed mode for debugging.

Automated Browser Contexts:

Playwright allows you to create isolated browser contexts for parallel execution of tests, saving time.

Powerful API:

Provides robust APIs to simulate user interactions like clicking, typing, hovering, file uploads, and more.

Built-In Test Runner:

Playwright Test includes a test runner with built-in features like parallel test execution, retries, fixtures, and more.

Cross-Platform:

Playwright supports Linux, macOS, and Windows, ensuring compatibility across development environments.

Network Interception:

Allows mocking API responses, testing different scenarios without requiring backend changes.

Visual Comparisons:

Supports screenshot comparisons for visual regression testing.

Language Support:

Playwright works with multiple languages like JavaScript/TypeScript, Python, Java, and C#.

Debugging Tools:

Comes with Playwright Inspector to debug tests visually and trace logs for easier troubleshooting.

Why Choose Playwright?

Reliable and Fast: Auto-waits for elements and browser states, reducing flaky tests.
Open Source: Free to use with an active community.
Full Stack Testing: Covers both frontend and backend testing (e.g., API testing).
Mobile Emulation: Emulate devices for responsive testing.

playwright

Nisrine_bg · 2025-01-29T20:09:39.423Z

Day 20 of 100daysofcode : How to Install Playwright

Installing Playwright

Get started by installing Playwright using npm, yarn or pnpm. Alternatively you can also get started and run your tests using the VS Code Extension.

1. ID Locator

2. Name Locator

3. Class Name Locator

4. Tag Name Locator

5. Link Text Locator

6. Partial Link Text Locator

7. CSS Selector

1. End-to-End Testing

2. UI/UX Testing

3. Integration Testing

4. Cross-Browser Testing

5. Continuous Integration/Delivery Pipelines

1. Use Custom Commands

2. Leverage Cypress Fixtures

3. Take Advantage of Assertions

4. Use Cypress Selectors Carefully

5. Handle Network Requests with cy.intercept

6. Utilize Cypress Plugins

7. Use .then() for Synchronous Commands

8. Take Screenshots and Videos

9. Parallelize Tests for Speed

10. Debugging with Cypress

Step 1: Install Node.js

Step 2: Create a Project Directory

Step 3: Install Cypress

Step 4: Open Cypress

Step 5: Write Your First Test

Step 6: Run Tests

Step 7: Configure Cypress (Optional)

Step 8: Add Cypress to Scripts (Optional)

Step 9: Integrate Cypress with CI/CD (Optional)

Step 10: Explore More Features

Key Points:

Prerequisites

Cypress Script

Key Features of the Script:

Run the Test

Key Features of Playwright

Why Choose Playwright?

Installing Playwright​

5. Handle Network Requests with `cy.intercept`

7. Use `.then()` for Synchronous Commands

Installing Playwright