It's impossible to say what's wrong without seeing:

1. Your HTTP(S) Test Script Recorder configuration along with the screenshot of the test plan
2. Your operating system proxy configuration (Chrome browser derives OS proxy setup)
3. JMeter.log file

So the only piece of advice I can give you is to use Recording Template feature, it's available from File -> Templates -> Recording entry of JMeter's main menu, it should generate a good setup which saves captured HTTP requests under the Recording Controller

You might find JMeter Chrome Extension easier to use, in this case you won't have to worry about proxies and certificates.

While recording scripts in JMeter, Mozilla Fire Fox is not accepting the JMeter certificate. I've all the settings configured correctly (Fire Fox's Proxy settings and importing JMeter certificate to Fire Fox). Note that I've the latest versions of everything (JMeter, Fire Fox as well as Java 16). I have tried re-installing JMeter, Fire Fox but it still not working. I have enabled "network.proxy.allow_hijacking_localhost" but its still not working. The only scripts that are being recorded are of Mozilla's certificate rejection. Please Help me out as using any any extension like Blazemeter is not an option.

If you extend a class having driver field where that field is initialized do not add filed of the same name to child class. Doing that you're hiding a field of base class.

Here is the example:

Your base:

public class TestBase {
public Object object;

@BeforeTest
public void doBefore(){
    object = new Object();
}

}

<p><strong>Your test that WILL fail (a.k.a BAD TEST):</strong></p>
<pre class="lang-java prettyprint-override"><code>public class TestChild extends TestBase{

    Object object;

    @Test
    public void doTest(){
        Assert.assertNotNull(object);
    }

}

Your test that WON'T fail (a.k.a GOOD TEST):
public class TestChild extends TestBase{
@Test
public void doTest(){
    Assert.assertNotNull(object);
}

}

Try this

WebElement element = driver.findElement(By.id("mousehover"));
        js.executeScript("arguments[0].scrollIntoView(true);", element);
        Thread.sleep(2000);
        js.executeScript("window.scrollBy(0, -190);");

For Screenshot, you have to use TakeScreenshot

File sourceFile = ((TakesScreenshot)driver).getScreenshotAs(OutputType.FILE);
FileUtils.copyFile(sourceFile, new File(directory + filename));

Oh, that's a long one.

Let's take two points of view:

• Pragmatic POV:

they insist on faster delivery

Saying that TDD would decrease delivery speed is not necessarily true.

If you search for studies on this, you will find a mixed bag of conclusions, highly dependable on the research methodology itself - this is the case because the code you write through TDD is not the same code you write with TLD (Test Last Development).

Thus, it's a false dichotomy - it depends on each particular context.

• Ethical POV:

For a longer discussion on this, I suggest watching Bob Martin's Craftsman's Oath talk. In a nutshell, the argument is that developers have the duty to his/her of demonstrating what capabilities of the software and the duty to his/her developer colleagues to ensure the software is kept in a state that they can work.

And these two duties can only be achieved* through TDD (or maybe even Test-Commit-Revert - TCR as Kent Beck shows).

The first because TDD/TCR limits the developer to only make progress in the production code based on one demonstratable behavior - if more behavior is added without a previous failing test, it's not TDD/TCR. Bugs will exist, for sure - but not bugs because of a misunderstanding between the programmer's intent and what he/she codes, because he/she coded the behavior twice (as a specialized test and as generic production code).

The second because only through TDD you can ensure you can safely refactor. Without the limitation above, you may never know if there is some behavior not demonstrated by tests. Without this certainty, all refactoring work is in the hope nothing will unnoticeably break. Line coverage and mutation coverage analysis could help, but they are not as complete as the TDD limitation.

* "can only be achieved": A necessary condition, not a sufficient condition.

If these two points are not relevant for your context, then TDD/TCR loses most of its reason to be.

If you want to have fast delivery, you may want to consider Continous Delivery. The idea is to keep your software always in a deliverable state. No hidden long-living branches, no half-done features (meaning we are not sure if it works as intended), etc. CD is a consequence of a broad set of practices which include TDD, Continous Integration, etc. Dave Farley Youtube channel and book can give you a good introduction.

• Will the developers slow down when first learning TDD? For sure.
• Will the developers feel frustrated when first learning TDD? For sure.
• Is there anything worth learning that doesn't make you slow down and frustrated during the learning process? No.

You're asking a lot fo concrete questions to which there're no universal answers. I'm afraid your question will be closed because of lack of focus.

I'll try to give you some pointers.

What should I first focus on as a beginner with no knowledge in automated testing? Should I first learn C#? Or start directly learn Selenium (or other testing tools?)

Focus on learning where automation can bring value and what information you can gather using it (ask around in your company). There's nothing worse than people who come to this area and start automating everything with no clear goal in mind.

Learn what the layers of the application are and what could you test and check on each one.

Since you mentioned UI, it seems to me that your focus will be on UI only. Learn to limit yourself on this level since checks tend to run long and are closely tight to UI changes, which more often than not means they also break often.

How much experience do I need in C#, to fully use Selenium? Is it enough when I know the basics in C#? Or do I need advanced/expert knowledge in C# for selenium?

You are a Tester, go and test yourself. Give yourself a task to automate something using these technologies. How easy was it? If you feel it was hard, you should probably study more.

Today, I had my first talk with a tester from a other team and he mentioned “Tosca”. I googled the difference between Tosca and Selenium. And both are being used very differently. Maybe someone here used both and could give me his opinion on both testing tools? Are both covering the same test cases?

C#, Tosca, Selenium, ... you mention a lot of technologies but no reasons why these were suggested. Focus on why. Choosing appropriate tools in your context can save you a lot of time later on. Why don't you ask that Tester to tell you why he chose Tosca, or C#, or any other tool? Don't be satisfied with answers such as "that's the way this company runs."

Are there any other tools needed for automated testing beside of Selenium or Tosca, which I should look at?

There're probably tens of other tools you'll (have to) learn. But you won't need all of them every single time. The problem here again is your context. You might use tool A now, but you might find tool B more appropriate on a future project.

All in all, I don't think that focusing too much on particular tools is especially beneficial. In my opinion, tools could be learnt fast, but it usually takes some time to develop the right attitude towards automation as well as the underlying technologies systems are built on.

If there are two test cases and the first one failed, in that case I don't want to stop the execution. What needs to be added?

Without using TestNG annotations, try/catch, using selenium only.

I finally found a solution by using actions and Keys.NUMPAD. Here is a sample of code:

phone=webdriver.find_element_by_id("phonenumber")
actions=ActionChains(webdriver)
actions.click(phone)
actions.send_keys(Keys.NUMPAD0)
actions.send_keys(Keys.NUMPAD2)
actions.perform()

This way i can submit the phone number like if i entered it manually!

I have created a script in Selenium IDE that goes to this page: https://www.lexology.com/instructcounsel/find and presses the 'Example' button and then asserts that results are displayed for the search. This script runs without a problem but when I export as Java to Selenium GRID then the assert fails.

The image taken by screenshot.java shows that none of the search results have loaded:

I am expecting:

This seems to be the case even if I add a wait for the element. I have tried also adding a js.executeScript but this hasn't helped. It looks like either the button is not being found and clicked or the asynchronous content is not loading.

Here is my exported script:

package com.lbr.testcases.lexology.experts.instruct_counsel;

import com.lbr.utils.Screenshot;
import java.util.*;
import java.net.MalformedURLException;
import java.net.URL;
import static org.hamcrest.CoreMatchers.is;
import org.hamcrest.MatcherAssert;
import org.junit.After;
import org.junit.Before;
import org.junit.Test;
import org.openqa.selenium.By;
import org.openqa.selenium.chrome.ChromeOptions;
import org.openqa.selenium.JavascriptExecutor;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.openqa.selenium.WebDriver;

public class instruct_counsel_example_anon {
  private WebDriver driver;
  JavascriptExecutor js;

  @Before
  public void setUp() throws MalformedURLException {
    driver = new RemoteWebDriver(new URL("http://host.docker.internal:4444/wd/hub"), new ChromeOptions());
    js = (JavascriptExecutor) driver;
    new HashMap<String, Object>();
  }
  @After
  public void tearDown() {
    Screenshot.TakeScreenshot(driver);
    driver.quit();
  }
  @Test
  public void searchinstructcounselexampleanon() {
    // GIVEN that I am an anonymous user on the Instruct Counsel page
    driver.get("https://www.lexology.com/instructcounsel/find");
    // WHEN I press the Example button
    driver.findElement(By.xpath("//div[@id='do-example-search']/button")).click();
    js.executeScript("window.scrollTo(0,579)");
    // adding a wait for the content to be displayed
    WebDriverWait wait = new WebDriverWait (driver, 60);
    wait.until(ExpectedConditions.elementToBeClickable(By.xpath("//h3[contains(.,\\\'3. Find your lawyer (746 matches found)\\\')]")));
    // THEN some example lawyers are displayed
    MatcherAssert.assertThat(driver.findElement(By.xpath("//h3[contains(.,\'David Zetoony\')]")).getText(), is("David Zetoony"));
    MatcherAssert.assertThat(driver.findElement(By.xpath("//h3[contains(.,\'3. Find your lawyer (746 matches found)\')]")).getText(), is("3. Find your lawyer (746 matches found)"));
  }
}

I recommend reading this post: https://github.com/TheBrainFamily/cypress-cucumber-preprocessor/issues/60 it deals with basically your situation with the exception that the same step definition names are in different files.

Although I haven't tried it myself now, it does seem from the discussion on the linked github page that cypress-cucumber in the past just used the first loaded step, but it was later changed in a way that you get an exception in such a situation. So it seems your example would not run and you'd receive "Multiple step definitions match" exception.

It'd be nice if you tried it and confirmed if this is true, so that we have all information even here in this question.