Error in criteria not found when retrieving data based on search

Tuhin, first of all, thank you very much for your interest. I tried your modified code again. However, I regret to say that unfortunately it still does not skip numbers that are not available. For numbers that are not found, the program simply stops working.

Talking about unit testing, it's a good practice to make your code more testable and modular. One way to achieve this is by introducing abstractions and dependency injection. In your case, you might want to introduce an interface or a delegate to represent the functionality of finding elements by specific identifiers. This allows you to create a mock or fake implementation for testing purposes.

I tried the modified codes. However, this time it does not skip the number that cannot be found and continue with the next number.

You can use a try-catch block to handle the exception when a number cannot be found. This way, if an error occurs, the program will skip the current iteration and continue with the next one. Here’s how you can modify your code:

drv.SwitchTo().Window(drv.WindowHandles.ToList().Last());

for (int i = 0; i < dataGridView1.Rows.Count - 1; i++)
{
    try
    {
        var val0 = dataGridView1.Rows[i].Cells[0].Value.ToString();
        drv.FindElement(By.Id("txtTC")).SendKeys(val0);
        Thread.Sleep(3000);
        drv.FindElement(By.Id("btnAra")).Click();
        Thread.Sleep(3000);

        if (val0 != null && val0 != string.Empty)
        {
            var val1 = drv.FindElement(By.Id("txtKisiTCKimlikNo")).GetAttribute("value");
            var val2 = drv.FindElement(By.Id("txtAdi")).GetAttribute("value");
            var val3 = drv.FindElement(By.Id("txtSoyadi")).GetAttribute("value");

            dataGridView1.Rows[i].Cells[1].Value = val1;
            dataGridView1.Rows[i].Cells[2].Value = val2;
            dataGridView1.Rows[i].Cells[3].Value = val3;

            // Rest of your code...
        }
    }
    catch (NoSuchElementException)
    {
        // Log the error or handle it as you see fit.
        Console.WriteLine($"Element not found for row {i}. Skipping...");
        continue;
    }
}

In this code, NoSuchElementException is caught when an element cannot be found. The program will then print a message to the console and skip the current iteration of the loop with the continue statement. You can replace the Console.WriteLine line with any error handling or logging code that suits your needs. Please note that you need to import OpenQA.Selenium to use NoSuchElementException. If there are other types of exceptions you want to catch, you can add more catch blocks. Remember to always handle exceptions responsibly to avoid hiding errors that might need to be fixed.

Thanks

To handle the scenario where an element is not found and avoid the program from crashing, you can use try-catch blocks to catch exceptions. Specifically, in your case, you can use a try-catch block around the code that might throw an exception when an element is not found. If an exception is caught, you can set the corresponding cell value to some default value or leave it empty.

drv.SwitchTo().Window(drv.WindowHandles.ToList().Last());

for (int i = 0; i < dataGridView1.Rows.Count - 1; i++)
{
    var val0 = dataGridView1.Rows[i].Cells[0].Value.ToString();
    if (val0 != null && val0 != string.Empty)
    {
        drv.FindElement(By.Id("txtTC")).SendKeys(val0);
        Thread.Sleep(3000);
        drv.FindElement(By.Id("btnAra")).Click();
        Thread.Sleep(3000);

        try
        {
            var val1 = drv.FindElement(By.Id("txtKisiTCKimlikNo")).GetAttribute("value");
            var val2 = drv.FindElement(By.Id("txtAdi")).GetAttribute("value");
            var val3 = drv.FindElement(By.Id("txtSoyadi")).GetAttribute("value");

            // ... rest of your data extraction code
        }
        catch (NoSuchElementException)
        {
            Console.WriteLine($"Number {val0} not found. Skipping to the next number.");
            continue;  // Skip to the next iteration of the loop
        }
    }
}

the FindElement method throws a NoSuchElementException (indicating the element wasn't found), the error is caught and the code can proceed. When the exception is caught, the continue statement skips the rest of the current iteration and moves to the next number in the loop, preventing the program from crashing. The Console.WriteLine statement within the catch block can be used to log or display a message indicating that a number was not found, aiding in debugging and tracking.

You should be using explicit waits (e.g., WebDriverWait in C#) instead of Thread.Sleep for more reliable element interaction and better performance.