VTune analyzer should work regardless whether the execution module is an EXE or a DLL, or a kernel driver. It collects data on whatever happens to be running in the system whether the Event Based Sampling collection is occurring.
I'm trying to understand the text starting,"...when i try to get modules related to Test.exe process...." In the normal progression of event sampling, you should get a process display, which I think is what you're referring to, so it sounds like Test is showing up on the process display. At that point you'd want to be sure that line was selected in the display and choose the module view. By default it should list all the load modules of the Test process in the order of hot spot "hits." If Vtune analyzer ever interrupted system while Text.exe was executing, it should collect one sample from Test.exe, more if more time is spent there. Regardless, since you orginally constructed the VTune analyzer project to launch Test.exe, it should already be listed among the modules of interest and so should have a slot in the module display, even if it didn't site any samples. If you don't see this then something went wrong. It might be, though, that Test.exe spends so little time executing that VTune analyzer doesn't catch a sample; unlikely but possible.