Hot answers tagged

4

In Cucumber 5.7.0 the support of tags is handled in different way so that expression(infix boolean expression) can also be used in the same way. You can pass the multiple tags like @CucumberOptions(tags = "@smoke and @positive") public class RunCucumberTest {} Another way to manage the tags by JVM System Property mvn test -Dcucumber.filter.tags="@smoke ...


4

This is an example of building a software system for the marketplace. In this case, you have many customers or users, each of which has its expectations for the system. However, someone must have identified that there is a need for the product in the marketplace. If someone did not justify the possible need or desire for the product, how did anyone fund the ...


4

Break it up. Just as importantly, however, see what unit and integration tests you can make. I see: confirmation form validations composition of email to a new user triggering email for a new user triggering of notifications to Administrator setting email status based on event trigger of analytics notification All of these should have unit tests to ...


3

Configuring the Unit Test Provider Tests are executed using a unit test provider. Add the corresponding NuGet package to your project to define your unit test provider: SpecRun.Runner SpecFlow.xUnit SpecFlow.MsTest SpecFlow.NUnit You can only have one unit test provider! Source: Executing SpecFlow Scenarios All these frameworks are supported , why would you ...


3

To answer to the main question: Both. Short, complete and test only thing. Avoid doing checks in different parts in the same test(check email + check back-end + check front-end) The first issue I see its the whey the scenario is defined (too many details, not following the BDD principles -> one of them is to define steps that are very easy to understand and ...


2

It is a good approach to split the complex scenarios in a set of short testcases. You can use the below-mentioned use-cases for your problem, that we will usually create for functional testing services in our software testing services company. Verify that new user/non-logged user should be prompted for the registration. Verify that new user should be able ...


2

Setting aside opinions people may have about SAFe and how Agile it really is, there is no conflict between SAFe as it is defined and TDD or BDD. In fact, the official safe write-up for teams suggests that software teams should be using those practices (https://www.scaledagileframework.com/agile-teams/). SAFe also still prescribes cross-functional dedicated ...


1

xUnit. ( ... or even unittest, pytest, if you would consider python: "unittest : A unit testing framework for Python. It is python’s xUnit style framework." )


1

I would go with different features. CAN you go with DB1.feature doing everything and then DB7.feature? Can you create employee and customer in one run on the same DB?


1

I don't recommend reusing sessions but you could do the login as part of your [OneTimeSetUp]/[AssemblyInitialize] in your test class and likewise [TearDown]/[AssemblyCleanup] the session (what you use depends on the 'Custom Tool' set on your .feature file). You can save what ever you want as a global like I outlined on a similar question. I did this once for ...


1

make sure you have installed cucumber for eclipse from market place: https://marketplace.eclipse.org/content/cucumber-eclipse-plugin Goto preference and search for cucumber and enable step detection


1

The two ways to avoid duplication are using: Background Using page object and creating wrapper function with all prerequisite Given('a web browser is at the Google home page', () => { homepage.goto() } When('the user enters "panda" into the search bar', () => { homepage.enter("panda") } Then('links related to "panda&...


1

It all depends on the logic you intend on testing, and when the test fails, how large an area of the application you'll need to investigate. A full end-to-end test verifies data on screen. Doing this in BDD certainly replicates that test, but the behavior is what BDD is about. What behavior are you testing? How many reasons does your test have to fail? If ...


1

In this case , The only need for testing the backend database is when you doubt whether the browser is actually getting the data from the database or is it simple caching it in cache or browser local storage. So, if you want to ensure that's not what is happening, then use driver.quit() and open a new driver instance. This will be a new instance with all ...


1

What's the problem then? Both xPaths seem functional. On the other hand, a good practice is to simplify it as much as possible, so it's readable for you in the future and for other people. The following xPath seems a bit more readable to me: //div[@id="opbox-category-tree"]//a[text()="Drukarki i skanery"] You don't need to write every element on the way ...


1

This is a common trap people fall into when writing behavior driven tests. You do not want to run entire scenarios as a prerequisite. Instead, you need to write one or more Given steps that simulate the things the other scenarios do. Without seeing an example of the login scenario, and one of the other scenarios requiring the user to log in I cannot give you ...


1

Feels like the generation of the code behind is not working correctly. Specflow creates .cs file for each .feature file. This .cs file contains the "real" testcode that is found by the test-explorer. Each should be regenerated on each save, rebuild. We had to set the option "specflowsinglefilegenerator" to true. Suggest you try the options in the following ...


Only top voted, non community-wiki answers of a minimum length are eligible