Software testing is my passion
API testing is an essential part of the software development lifecycle, focusing on the communication and data exchange between different software systems. It verifies that APIs are functioning correctly and meeting performance, reliability, and security standards. Using C# with the RestSharp library simplifies the process of interacting with RESTful APIs by providing an easy-to-use interface for making HTTP requests.
Introduction
In today’s fast-paced software development environment, manual test case generation struggles to keep up with the ever-increasing complexity of systems, especially in Agile and DevOps-driven projects. AI-driven test case generation has emerged as a powerful solution to streamline and automate this process, leveraging artificial intelligence and machine learning (ML) to improve test accuracy, efficiency, and coverage.
This lecture will explore AI-driven test case generation, how it works, its advantages and challenges, and its application in modern testing environments.
AI-driven test case generation automates the creation and optimization of test cases using AI techniques such as machine learning (ML) and natural language processing (NLP). By analyzing historical data, code structure, requirements, and user behavior, AI tools can produce test cases that cover critical functionalities, saving time and effort for testing teams.
Instead of manually writing test cases based on predefined requirements, AI-driven approaches can dynamically generate tests that adapt to the code, highlighting the most important areas to test, and identifying risks that human testers might overlook.
AI-driven test case generation is transforming how software testing is performed. By leveraging AI’s ability to analyze data, adapt to changes, and optimize testing efforts, teams can increase test efficiency, improve coverage, and reduce the time and cost of testing. However, while AI offers many advantages, it requires proper setup, high-quality data, and a clear strategy to maximize its benefits.
Incorporating AI in test generation is becoming essential in today’s fast-evolving software landscape, especially in Agile and DevOps workflows.
As technology continues to evolve at a rapid pace, the demand for quality software has never been greater. In response to this need, I’m excited to announce that I will be leading a series of lectures on Quality Assurance (QA) and Software Testing at Uttara University under the EDGE project.
Quality Assurance is more than just finding bugs; it’s about ensuring that software meets the highest standards of quality and reliability. With the increasing complexity of software applications, effective QA practices are essential for delivering products that not only meet user expectations but also perform well under real-world conditions.
Throughout this course, we will explore key concepts and methodologies in QA and software testing, including:
By the end of this course, students will be equipped with the knowledge and skills to:
I am passionate about sharing my knowledge and experiences in QA and software testing. This course will not only provide theoretical insights but also hands-on experience that prepares students for careers in this vital field.
I look forward to engaging discussions, collaborative projects, and fostering a deeper understanding of quality assurance among aspiring software professionals.
Stay tuned for updates, and let’s embark on this journey towards achieving excellence in software quality together!
Visual Studio offers a feature called “Paste Special” that allows you to easily generate C# classes from JSON objects. This is particularly useful when working with web APIs or any JSON data, as it automates the creation of data models that match the JSON structure.
MyClass.cs).
In the dynamic world of software development, Agile methodology has become the gold standard for delivering iterative, customer-centric products. While Agile emphasizes collaboration, flexibility, and continuous delivery, one critical element often underestimated is the role of Software Quality Assurance (SQA).
Far from being a traditional gatekeeper at the end of the development cycle, SQA in Agile is a continuous, collaborative force that ensures product quality from Day 1. Here’s how SQA contributes meaningfully across the Agile lifecycle:
In Agile, quality is everyone’s responsibility—but SQA takes the lead from the start. Testers participate in sprint planning, backlog grooming, and story estimation, ensuring that acceptance criteria are testable and clear.
Benefits:
Agile favors rapid iteration. That’s where continuous testing comes in. SQA builds and maintains test automation frameworks that run across CI/CD pipelines, enabling fast feedback loops.
Key practices:
In Agile, SQA doesn’t work in silos. Instead, testers collaborate closely with developers, product owners, and UX designers in a shared sprint team. They raise concerns proactively, influence technical decisions, and advocate for testability.
Contributions include:
Beyond scripted tests, SQA performs exploratory testing to uncover edge cases and usability flaws that automated scripts might miss. Agile welcomes changing requirements, and exploratory testing is agile enough to keep up.
Impact:
Each Agile sprint ends with a retrospective. SQA contributes by analyzing defect trends, test effectiveness, and root causes. This feedback loop helps the team refine processes, tools, and test strategies over time.
Common SQA metrics in Agile retros:
SQA identifies risks early—not just technical bugs, but also requirements volatility, environmental instability, and integration complexity. They ensure mitigation strategies are in place before these risks snowball into blockers.
Tools and techniques:
In Agile, success is measured by working software that delivers value. SQA bridges the gap between business and technology by:
In Agile, Software Quality Assurance is not a phase—it’s a mindset.
SQA professionals play a strategic role in maintaining speed without sacrificing quality. By embedding testing within sprints, collaborating continuously, and leveraging automation and feedback, SQA helps Agile teams build better, faster, and smarter software.
In the end, it’s not just about catching bugs—it’s about delivering confidence with every sprint.
In today’s interconnected software ecosystems, APIs (Application Programming Interfaces) are the backbone of communication between services. Ensuring their performance, security, and functionality through API testing is critical. Whether you’re a developer, QA engineer, or tech enthusiast, understanding the spectrum of API testing techniques helps deliver robust and reliable software.
This guide explores the 15 essential types of API testing, complete with descriptions, workflows, and their unique purpose.
Purpose: To verify if the user interface that interacts with the API works correctly.
Purpose: To ensure each API function performs as expected.
✅ Best For: Verifying correctness of API responses.
Purpose: To check API behavior under normal or peak load conditions.
Purpose: To evaluate API stability under extreme or high load conditions.
Purpose: To check if the basic functionality of the API is working.
Purpose: To test data flow between multiple modules or services using APIs.
Purpose: To ensure the final product meets business and functional requirements.
Purpose: To test the API’s resilience to unexpected or invalid data.
Purpose: To identify vulnerabilities and protect data integrity.
Purpose: To confirm recent changes didn’t break existing features.
Purpose: To identify runtime issues, errors, or performance glitches.
Purpose: To verify if APIs work well with diverse systems or environments.
Although already mentioned above, this type plays a vital part in every build/deployment pipeline, especially during CI/CD where a quick validation saves time.
Even though UI testing is typically separate, modern testing often involves correlating UI interactions with API responses to ensure true end-to-end validation.
API testing should not be siloed. Real success lies in orchestrating various test types together—e.g., running regression tests after load tests, or security checks during integration cycles.
Popular Tools:
Conclusion:
API testing is more than just calling endpoints. It’s a multifaceted approach involving performance, security, reliability, and usability. Mastering these 15 types of API tests empowers you to build future-ready applications that scale confidently and perform under pressure.
Software testing is the backbone of delivering reliable, secure, and user-friendly applications. It ensures that the software meets expectations, both technically and functionally. This guide explores the two primary categories of software testing—Functional and Non-Functional Testing—and outlines core types under each, complete with real-world examples and use cases.
Definition: Functional testing focuses on testing the software against the business requirements. It answers the question: “Does the system do what it’s supposed to do?”
Definition: Non-functional testing focuses on how the system performs under various conditions rather than what it does.
| Testing Type | Category | Performed By | Example Use |
|---|---|---|---|
| Unit Testing | Functional | Developers | Login method returns correct token |
| Regression Testing | Functional | QA | Old checkout flow after adding discounts |
| Load Testing | Non-Functional | QA | App supports 1000 concurrent users |
| Security Testing | Non-Functional | Security Team | Prevent SQL injection |
| UAT | Functional | End-Users | Final confirmation of a sales dashboard |
| A/B Testing | Specialized | Marketing/Product | Choose best email subject line |
Mastering the different types of software testing is essential for delivering bug-free, scalable, and user-friendly software. A balanced mix of functional, non-functional, and exploratory testing ensures high-quality releases and happy users.
Below is the text box and the corresponding HTML:
If I used sendkeys, sometimes it may not working
driver.findElement(By.name(“mainphone”)).sendKeys(“(02)2222-2222”);
driver.findElement(By.id(“mobilephone”)).sendKeys(“05-5555-5555”);
If sendkeys() methods are not working then use following two ways to input text:
Before sendkeys() use click() method to click inside textfield i.e:
driver.findElement(By.name("mainphone")).click();
driver.findElement(By.name("mainphone")).sendKeys("(02)2222-2222");
driver.findElement(By.id("mobilephone")).click();
driver.findElement(By.id("mobilephone")).sendKeys("05-5555-5555"); Hi guys, I am going to run a test mobile emulator with selenium and VS C#
Import
using System;
using System.Threading;
using NUnit.Framework;
using OpenQA.Selenium;
using OpenQA.Selenium.Support.UI;
using OpenQA.Selenium.Chrome;
Driver Utils Class
First of all delclaring the webdriver, which will be used for open specfic browser
namespace SeleniumAutomation
{
[TestClass]
public class Setup
{
IWebDriver webDriver;
}
}Open Chrome
[Test]
public void Open_Browser()
{
webDriver = new ChromeDriver();
}Open Chrome Mobile Emulator
[Test]
public void Mobile_Emulator_Browser()
{
ChromeOptions chromeCapabilities = new ChromeOptions();
chromeCapabilities.EnableMobileEmulation("Pixel 5");
webDriver = new ChromeDriver(chromeCapabilities);
}I think it will be helpful to run chrome in mobile emulator
I have a string Sample Text (Loren) and I want to extract the text between the brackets, how would I do this?
string input = "Sample Text (Loren)";
string output = input.Substring(input.IndexOf('(') + 1, input.IndexOf(')') - input.IndexOf('(') - 1);