SoftTree Technologies SoftTree Technologies
Technical Support Forums
RegisterSearchFAQMemberlistUsergroupsLog in
[10.0.187 Pro] - Unit Testing problems

 
Reply to topic    SoftTree Technologies Forum Index » SQL Assistant View previous topic
View next topic
[10.0.187 Pro] - Unit Testing problems
Author Message
gemisigo



Joined: 11 Mar 2010
Posts: 1506
Country: Hungary

Post [10.0.187 Pro] - Unit Testing problems Reply with quote
I'm experiencing serious issues with Unit Testing feature.

The most critical is that I cannot save unit test projects. SA asks for a path and a file name but it simply does not save the file. As a consequence, I cannot load projects either, as there's nothing to load. I have to rebuild the unit tests from scratch every time the unit tester is started. Another consequence of that is SA also keeps complaining about the project having been changed and asks if I want to save it. Which I'd like to, but it does not happen.

I tried and loaded some unit tests that were saved with earlier versions of SA and those load properly. However, those do not test my current project and any changes made to them are not saved either, the files remain "unscathed".

Saving test results to a database table doesn't seem to work either (at least in Oracle).


Last edited by gemisigo on Thu Oct 18, 2018 8:01 am; edited 1 time in total
Thu Oct 18, 2018 5:13 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 6796

Post Reply with quote
Is that issue specific to Unit Test projects only? Can you save other files, for example SQL files or types of project files?
Have you tried different file locations? Same result?
Thu Oct 18, 2018 7:59 am View user's profile Send private message
gemisigo



Joined: 11 Mar 2010
Posts: 1506
Country: Hungary

Post Reply with quote
It only affects Unit Test projects, yes. I can save sql files without any problems. I don't know what other project types are there. I've tried several locations with the same result, that is, without any.

EDIT:
I tried to save the unit test project under the name 'ideveled_nanana' and used Process Monitor to capture what happens. This is what it caught:

Quote:

14:20:31.7514914 Explorer.EXE 7512 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.1524831 SqlEditor.exe 2604 CreateFile T:\TMP\.kuka\ideveled_nanana NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.1572014 SqlEditor.exe 2604 CreateFile T:\TMP\.kuka\ideveled_nanana NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.1574163 SqlEditor.exe 2604 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.1576140 SqlEditor.exe 2604 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.1597476 SqlEditor.exe 2604 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest SUCCESS Desired Access: Generic Write, Read Attributes, Disposition: Create, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: 0, OpenResult: Created
14:20:36.1600337 SqlEditor.exe 2604 CloseFile T:\TMP\.kuka\ideveled_nanana.unittest SUCCESS
14:20:36.1602723 SqlEditor.exe 2604 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest SUCCESS Desired Access: Read Attributes, Delete, Disposition: Open, Options: Non-Directory File, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
14:20:36.1603397 SqlEditor.exe 2604 QueryAttributeTagFile T:\TMP\.kuka\ideveled_nanana.unittest SUCCESS Attributes: A, ReparseTag: 0x0
14:20:36.1603737 SqlEditor.exe 2604 SetDispositionInformationFile T:\TMP\.kuka\ideveled_nanana.unittest SUCCESS Delete: True
14:20:36.1604140 SqlEditor.exe 2604 CloseFile T:\TMP\.kuka\ideveled_nanana.unittest SUCCESS
14:20:36.1857672 Explorer.EXE 7512 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.7536261 Explorer.EXE 7512 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.7563550 Explorer.EXE 7512 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
14:20:36.8095015 Explorer.EXE 7512 CreateFile T:\TMP\.kuka\ideveled_nanana.unittest NAME NOT FOUND Desired Access: Read Attributes, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a



EDIT2: After a few tries I also got an exception. I've sent it, and it got issue tracking number: 34984.
Thu Oct 18, 2018 8:05 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 6796

Post Reply with quote
Thank you very much for the details. We are looking into that issue. I will get back to you as I have any updates.
Thu Oct 18, 2018 8:32 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 6796

Post Reply with quote
Hello. This issue is specific to 64-bit versions of SQL Assistant. Please use 32-bit version to save unit test projects. You can then run them with both 32-bit and 64-bit versions
Fri Oct 19, 2018 1:19 am View user's profile Send private message
gemisigo



Joined: 11 Mar 2010
Posts: 1506
Country: Hungary

Post Reply with quote
I see. Switching back and forth between 32/64 to just save and use unit test projects will become inconvenient in the long run. I'll also have to acquire 32-bit version of different drivers which takes time and might prove to be difficult for some cases.

Is there a fix planned for this issue? Are there any other drawbacks/advantages for using the 64-bit version or for 32-bit version? I'd rather use one of them, not both.
Fri Oct 19, 2018 5:20 am View user's profile Send private message
SysOp
Site Admin


Joined: 26 Nov 2006
Posts: 6796

Post Reply with quote
Yes, it's certainly going to be fixed. It turned out to be caused by 64-bit code compiler bug in some optimization routine. We will have a fix for it soon.
Fri Oct 19, 2018 9:27 am View user's profile Send private message
gemisigo



Joined: 11 Mar 2010
Posts: 1506
Country: Hungary

Post Reply with quote
That's a great relief for me. It seems I'm pretty lame when it comes setting up connections to Oracle. I struggled when doing it 64-bit and failed with 32-bit completely :(
Fri Oct 19, 2018 4:33 pm View user's profile Send private message
Display posts from previous:    
Reply to topic    SoftTree Technologies Forum Index » SQL Assistant All times are GMT - 4 Hours
Page 1 of 1

 
Jump to: 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


 

 

Powered by phpBB © 2001, 2005 phpBB Group
Design by Freestyle XL / Flowers Online.