I think the problem is how the organization or team thinks about testing. It's not an activity that should be done only by a specific role we call a Tester.

You said you work in an agile environment, yet all the testing is unloaded onto Testers. Why don't developers write tests for their own code? Why the team doesn't get together to figure out how to best test the app in your context? How can you change this approach so that testing is a teamwork? I think these are the questions what should be answered in the first place.

I don't know if 5000+ GUI tests is too much for this context, but it does look like it, especially when there're only 2 people and previous attempts failed (as mentioned in the comment section). Why repeat the same approach again? It will likely bring same results, that is one of a failure.

However, I'd suggest some middle-ground solution for now. You'll likely have some GUI checks anyway, perhaps you can create just a few of them that bring the most value and information to the team.

I am trying to login android application on emulator hosted on Windows OS. Facing below error :

I/ConversationToQueryExtension: ConversationToQueryExtension.isEnabledForHostApp():252 Conv2Query not enabled due to current app [com.intelligentworkforce] not in whitelist

Please let me know if anyone face/fix this issue.

Disclaimer: There is no standard / widely accepted precise definitions. The best you can do is to learn about the nuances of different contexts, have your own definitions precisely, but when hearing someone, pay attention to what they think each of these things mean - possibly filling the gaps of some points.

Here go some points I see many people use:

• Unit Test

The book XUnit Patterns, by Gerard Meszaros, says the following about Unit Test:

A test that verifies the behavior of some small part of the overall system. What makes a test a unit test is that the system under test (SUT) is a very small subset of the overall system and may be unrecognizable to someone who is not involved in building the software.

The last part connects to Bob Martin's definition: A test made by programmers for programmers.

These tests are characterized by language that makes sense to the internals of your software: The entities that make your architecture and how they behave.

The C2 Wiki has many other definitions.

unit testing is about testing individual functions with mock services

Not necessarily. Mocking is one way to design unit tests, known as the London school/style. You can read more about it here. To embrace both London and Chicago schools, I would recommend the focus on how are the writers and readers of these tests.

• Component Tests

Meszaros says the following about Component:

A larger part of the overall system that is often separately deployable.... A component can and should be verified using component tests before the overall application is tested using customer tests.

Additionally, about Component Test:

Contrast this with a customer test which is derived almost entirely from the requirements and which should be verifiable by the customer. And with a unit test which verifies a much smaller component. A component test is somewhere in between.

I hear this term very often in frontend frameworks. They usually allow creation of renderable objects they call Components. Imagine for instance the Search Bar here in Stack Exchange: It has behavior, can be rendered, etc, but it is not tightly coupled with any user flow - one can inject test doubles to mock the a backend service and get fake responses related to whatever we want. Component tests for it would render only this Component and exercise its logic (without mentioning customer related user flows).

• System Test

Meszaros calls those Customer Tests:

A test that verifies the behavior of a slice of the visible functionality of the overall system. The system under test (SUT) may be the entire system or a fully-functional top-to-bottom slice (or "module") of the system. A customer test should be independent of the design decisions made while building the SUT. That is, we should require the same set of customer tests regardless of how we choose to build the SUT. (But how the customer tests interact with the SUT may be affected by high-level software architecture decisions.)

In summary, these are the tests that talk the language of the customer and exercise the SUT as the user would (which is regardless of how we choose to design the system internally). Note that it doesn't necessarily mean touching the UI, because the UI is a detail - the business logic is not on the UI (at least not for a long time, because if it is, soon the developers will get stuck and not progress).

Dave Farley explains it in more detail here (he calls it Acceptance Testing).

I want to click on an element which contains class and title in selenium python.

A webpage contains certain folders with unique name. I want to click on a folder by specifying its name or title. Below is the html tag. I tried many ways but I am ending up with errors.

<div class="folder">
<p>
<a alt="ABC" title="ABC">ABC</a>
</p>
</div>

Initially, it used to work with below :

driver.find_element_by_xpath("//a[@title='ABC']").click()

But now it says unable to locate element. Please help me to solve this.

Error:

"selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element"

Firstly, in order to ensure the problem does not come from the cypress-get-table plugin, you could assert with "normal Cypress" that the table exists:

cy.get('im-data-table.hydrated')
    .shadow()
    .find('div#dataTable')
    .should('exist')

Secondly, I think the assertion you are using is incorrect - the tableData should be the variable in the assertion function, not the function itself:

cy.get('im-data-table.hydrated')
    .shadow()
    .find('div#dataTable')
    .getTable()
    .should(function(tableData){
        expect(tableData).to.be.empty
    })

Finally, your im-data-table.hydrated is itself in a shadow DOM, which you have to enter - so you have to chain multiple .shadow() calls:

cy.get('im-page.hydrated')
    .shadow()

    .find('...') // the im-section you're interested in
    .shadow()

    .find('im-data-table.hydrated')
    .shadow()

    .find('div#dataTable')
    .getTable()
    .should(function(tableData){
        expect(tableData).to.be.empty
    })

Of course, you can wrap all that code in a function.

I have a thread group with 30 Http request. I would like to run the whole thread group once with just 1 user, than wait 30 minutes, run it again, wait 30 minutes and so on for few days.
How should I configure my Thread group properties?

Thanks for you help.

Martin

it's not possible to "provide solution for same" without seeing:

1. Initial test plan
2. Test plan after adding CSV Data Set Config(s)
3. Results file from both executions
4. Just in case jmeter.log file

Per se CSV Data Set Config won't generate extra requests unless you have a While Controller configured to loop until there are entries in the CSV file.

Also be aware that you can limit JMeter test duration using 2 approaches:

1. "Specify thread lifetime" input at Thread Group level:

   

2. Use Runtime Controller which controls for how long are its children allowed to run

   

In both aforementioned cases the test won't last longer than 5 minutes

To gather the items for your list it looks like you don't need to be specific. Try something like this:

List<WebElement> options = driver.findElements(By.xpath(//*[contains(@id,"mat-option-")]));

That will populate your options List with all the elements that have an ID that contains mat-option-

1. The most straightforward option is installing your application into Android Emulator or iOS Simulator, this way the "virtual" handheld device will be using your machine's Internet connection and you will be able to capture the traffic with JMeter

2. You can go for so called "reverse USB tethering", refer the following guides:

   • How to use Windows' internet on Android phone through USB cable
   • iPhone Connecting to Internet Using Windows PC’s Network through USB Cable

3. If your application backend is publicly available the fastest and the easiest way would be using a 3rd-party recording solution like BlazeMeter Proxy Recorder

This is a standard programming practice intended to reduce bugs in code. As a refresher, the final modifier prevents a primitive variable or object reference variable from being reassigned. Thus, primitives are immutable, and a reference can ever point to the object it initially pointed to. (This does not affect what methods you can call, even ones that would mutate the object's internal state.)

Every IDE I've used in the past 10 years has had the ability to inspect the code in a method and deterministically apply the final modifier to a local variable that is not reassigned after it is initialized. The idea behind this is that if you wrote code, and saved it (which runs save actions that apply the final modifier) you probably don't mean to modify that variable again. If you DO intend to modify that variable, you can simply remove the modifier. Under this logic, every variable is final until someone actively decides it should not be.

As with all things programming, there are counter arguments to this. One is it clutters the code, increasing the workload on a programmer trying to read the code to maintain it. While this hasn't been my personal experience with this modifier, I know it has been with other practices for me so I don't want to dismiss this outright simply because it doesn't apply to me. The other is that if you only use it on ones that you decide should be final (as opposed to blanketing the code with final) you're sending a message to other developers that this variable should never change - that it should stand out among other variables as one you should not attempt to change.

PDHide's comment about limiting the use of parallel execution is related - final variables are eligible to be used in lambdas and parallel processing while other variables are not. Now I believe (it's been a while) the Java compiler will allow you to use a variable that is effectively final even if it is not explicitly final but then if someone decides to modify the variable before the parallel execution, the compiler can no longer say that it's effectively final and thus no longer eligible for the parallel processing and will throw a compile error. Easily fixed, but can be annoying nevertheless.

At the end of the day, you will want to have a brief conversation with your team to decide what will work best for you. The keyword has zero impact on the actual execution or efficiency, and it's all a matter of programmer productivity.