Welcome Guest! To enable all features please Login or Register.



Code with dynamic loading doesn't work as expected on grid nodes
#1 Posted : Thursday, August 24, 2023 6:09:06 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/11/2012(UTC)
Posts: 94

Thanks: 28 times
Was thanked: 12 time(s) in 12 post(s)

We have a project which is tested via end to end tests using playwright. The site has a system for overriding views in site specific libraries. When running locally everything works ok, but when I try and run the tests on grid nodes I find that the pages don't render currently because the DLLs that contain overriding views or view components are not loaded.

I assume this is because ncrunch is running the tests and keeping other DLLs in separate locations so they are not discovered.

What I don't understand is why the behaviour is different in the grid nodes and if there is anything I can do to make the behaviour the same?


#2 Posted : Thursday, August 24, 2023 8:57:43 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,015

Thanks: 937 times
Was thanked: 1262 time(s) in 1174 post(s)
Hi Sam,

The grid nodes are designed to operate with the same structure as the NCrunch client, in that they have a replica of your solution and they separate the projects into workspaces. All build, test, and dependency handling logic is the same.

Where the nodes are different from the client is in the environment. For example, they may have a different install state of other software, different assemblies in the GAC, etc.

What I would suggest is hooking a debugger onto your code as it runs on your client machine under NCrunch (ideally some time late in the test run). Break into the code and examine the list of running modules. Check the loaded locations of the modules that the grid node is having trouble resolving and see where they are. You might find that these libraries are stored differently on the node or are absent outside of the files being copied over from the client. It might be something as simple as a missing SDK on the node that NCrunch can't automatically copy over and needs to be installed manually.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.024 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download