TechTalk | Online discussion forum built with React & Google Firestore | State Container library

Possibly you need to add some wait.
Try adding

You have a order problem. SpecFlow creates an instance of the LoginSteps class to call the BeforeScenarioHook method Startup. But when it does that, it executed the constructor where you want to create an instance of the LoginPage, which want to resolve the WebDriver.

But at this point in time, the webdriver is not yet registered in the container and can't be resolved.

I would move the line loginPage = new LoginPage(container); into the hook to solve this problem.

The problem appears to be that you are stashing the IWebDriver object in the FeatureContext. The FeatureContext is created and reused for each scenario in a feature. While on the surface it appears safe for running tests in parallel using NUnit (which does not run scenarios in the same feature in parallel), my hunch is that this is not as safe as you think.

Instead, initialize and destroy the IWebDriver object with each scenario, rather than feature. The ScenarioContext should be thread safe, since it is created once for each scenario, and is only used for one scenario. I would recommend using dependency injection instead:

You have probably some old leftover files from before the update in your obj and bin folder.

• Close Visual Studio
• delete the folders
• start Visual Studio
• Rebuild Solution

After that, you should be able to execute your tests again.

You are missing the [Binding] Attribute on your step class.

it means somewhere you are using send_keys(filepath) and the file doesn't exists in that path

see if you are using this some where

var element = xdoc.Elements("Source").FirstOrDefault();

Given your provided XML elements will always be null and so you do nothing with your XML and that's why the result looks like the input.

Reason1: Elements() is looking for direct children only and is not a direct child in your doc.

See https://docs.microsoft.com/en-us/dotnet/api/system.xml.linq.xcontainer.elements?view=net-5.0

Reason2: tag has a different namespace than the doc itself and so the query is looking in the wrong namespace.

Solution:

The reason you get this error is that SpecFlow.Allure does not yet work together with SpecFlow 3.4. The dependency on the NuGet package with >=3.3.57 is wrong.

We made changes in SpecFlow to 3.4 that are not compatible with 3.3.

The GitHub Issue for this is here: https://github.com/allure-framework/allure-csharp/issues/133

As long as Allure doesn't update the NuGet package, you have to go back to SpecFlow 3.3.

There are only two riscv triple defined in llvm/include/llvm/ADT/Triple.h: riscv32 and riscv64.

By default HasStdExtV which is the flag corresponding to experimental-v in initialized to false in llvm/lib/Target/RISCV/RISCVSubtarget.h, if you want to use this extension you need to enable this feature.

Clangs seems also supporting this feature. In clang/lib/Driver/ToolChains/Arch/RISCV.cpp you can see that march support v feature and generate experimental-v for llc.

There is nothing in include/llvm/IR/IntrinsicsRISCV.td about Vector extension , however you can find the description of the instructions from the standard 'V' Vector extension in llvm/lib/Target/RISCV/RISCVInstrInfoV.td. It still experimental. In clang also you can find that even if the v extension is supported, in the default you can see // Currently LLVM supports only "mafdc". in clang/lib/Driver/ToolChains/Arch/RISCV.cpp