UI and integration test

[GeorgeS2019]

For new users straight to this project, will not realize how extensive the test framework, e.g. UI testings, mouse, keyboard controls.

I assume many of these tests in c# are still available in the gdunit4 projects.

[MikeSchulze]

Why it should not realize? ... It is all documented.
Check the README.md

I'm working on a new example projects to provide showcases, but it is in a very early state.

[GeorgeS2019]

I try to rename an external project to GdUnit4ApiTest so that the utility classes needed for godot dependent scene unit tests could be taken out of nuget and allow to access the internal sealed classes needed to run the godot dependent scene unit tests. Yet, these tests are ignored

[GeorgeS2019]

To use utility class for godot scene unit tests, I need to change the project name of an arbitrary classlib project to : GdUnit4ApiTest

using System.Runtime.CompilerServices;

[assembly: InternalsVisibleTo("GdUnit4ApiTest")]
[assembly: InternalsVisibleTo("GdUnit4.TestAdapter")]
[assembly: InternalsVisibleTo("GdUnit4.Analyzers")]
[assembly: InternalsVisibleTo("GdUnit4Analyzers.Tests")]

[GeorgeS2019]

I have this problem because I could not simply git clone the project and compile immediately.

[MikeSchulze]

To use utility class for godot scene unit tests, I need to change the project name of an arbitrary classlib project to : GdUnit4ApiTest

using System.Runtime.CompilerServices;

[assembly: InternalsVisibleTo("GdUnit4ApiTest")]
[assembly: InternalsVisibleTo("GdUnit4.TestAdapter")]
[assembly: InternalsVisibleTo("GdUnit4.Analyzers")]
[assembly: InternalsVisibleTo("GdUnit4Analyzers.Tests")]

It is intentional that not all classes are visible; it makes no sense to use internal classes from the gdunit4 API.
Everything should be usable as described in the documentation. I don't understand your problem.

[MikeSchulze]

so that the utility classes needed for godot dependent scene unit tests could be taken out of nuget and allow to ac

I don't get your point here. Which utility classes you mean?

[GeorgeS2019]

If you could Fork these projects and make the necessary adjustment so that most if not all the godot scene unit tests can run immediately after compile. If possible, provide comments why and where the users are wrong and incompatible with gdunit4net.api 5.0 version

[GeorgeS2019]

These users read the documentation and develop projects. Ideally they all should lead to ready to go. Got clone, and then compile and then all tests should run. But they do not!!

[MikeSchulze]

These users should join the Discord server to request assistance. I do not have the time to verify that all users are using the API correctly.
I am happy to assist via Discord, but it often turns out that users lack knowledge about project setup or C# in general. Many do not even read the documentation.

[MikeSchulze]

These users read the documentation and develop projects. Ideally they all should lead to ready to go. Got clone, and then compile and then all tests should run. But they do not!!

Can you please be more detailed with your answers.
Which project you mean?

[GeorgeS2019]

The documentation show youtube tutorial
https://github.com/ACG8/3d-platformer-with-gdunit4

this is not gdunit4net

[MikeSchulze]

No one is saying this is gdUnit4Net?

[MikeSchulze]

@GeorgeS2019 I would suggest discussing everything further in person via Discord, which would make it a lot easier than writing ping-pong messages here.

[GeorgeS2019]

@shekohex

after upgrading to 5.1.0-alpha2, many tests no longer ignored

https://github.com/shekohex/DMapGodot

[shekohex]

To be honest, 85% of that code was AI Generated, and I had to fix some of it, I suggest you check the original repo on my git host, they should be synced together, but just in case, because I have fixed several issues there. About testing, I don't think I should upgrade now to 5.1, maybe after being stable first.

[GeorgeS2019]

Before upgrading, many tests requiring Godot was ignored and this problem was fixed in the latest nugget 5.1.0 alpha version