isat | Satellite Orbit Tracker : implement most-current SGP models | Data Visualization library

This does sound like too many if statements. Here are some suggestions:

1. You should remember where the ant is in a variable. I don't think you need any if statements to check which cell the ant is in.

2. You should remember where the ant was last in a different variable.

3. You should make a list of the surrounding points and their smell points. Then remove from this list the ants previous location.

4. Using the above collection, you can loop through to pick the right one or if there is more than one choose one at random from the collection.

When you move the ant, set the previous location to the current location and then update the current location.

It's important to read the exception message carefully. The exception is not related to pico container. But rather pico container is telling you about a problem with your step definitions.

Probably you need to check out something like bulk routes for the API. So e.g. you can set the array of match_ids and make only one request and get the array of data.

Otherwise you need to wait for each request to be executed.

I see one big disadvantage - you cannot run your tests parallel. If you have a static driver that means, you can execute only one test at the time. One of the rules of tests is that test should not be dependent on any other test. It would be violated.

So what are the choices? I prefer to chain the methods, to make it more fluent. Let's assume that the LoginPage looks like this:

Can't I use Include() anymore? Is it better I start to using raw SQL commands?

That's not related to Include() but because you're using GroupBy(m=> m.Name). See breaking chagnes.

Here's a description about Groupby quoted from the official docs:

The SQL GROUP BY is restrictive too. It requires you to group only by scalar values.The projection can only contain grouping key columns or any aggregate applied over a column. EF Core identifies this pattern and translates it to the server

To fix that issue, you should use aGroupBy() that can be translated into SQL:

You can achieve this without passing the method, you need to modify your attribute slightly. I changed the attribute to take all the roles you want to test and return them in the data. Here is an example

From https://xunit.net/docs/shared-context#class-fixture

You can use the class fixture feature of xUnit.net to share a single object instance among all tests in a test class

Notice in a test class

In you case you have two separated classes HomeTest and ProfileTest, regardless of both are derived from same abstracted class, they are treated by xUnit as two different test classes.

Consider to use Collection Fixtures instead.
https://xunit.net/docs/shared-context#collection-fixture

You can use the collection fixture feature of xUnit.net to share a single object instance among tests in several test class

You can kind of do this, but just because you can do something, it does not mean it is a good idea. Think if it really makes the code easier to understand or not. Sometimes the amount of abstraction makes it just not worth it

It makes and returns a new instance, but the way to access this getter is a static method.

The property "Dashboard" is static, that means that you can access it from the class definition and you do not need an instance of the "Pages" class to get to it.

But because the property is a getter that runs a function, and because that function returns a new instance every time, you end up with a new instance each time.