Perform acceptance testing on v1.76 to ensure the app functions as expected before releasing the stable version. I will be going through this list and marking each completed section.
If you would like to help with testing, please test a full section (bullet point) at a time and report back with your findings. Please report any issues in this issue with the mRemoteNG version that you tested with. If you are unsure about how a feature should behave or think that there may be a bug, feel free to ask about it. If bugs are found and verified we can create a new issue to track the fix.
https://github.com/mRemoteNG/mRemoteNG/wiki/Acceptance-Testing
Almost done with File menu testing, just need to test the export feature a bit more.
1.76.4.16229 - tested _File Menu_ section on _Windows 10 LTSB 2016_ with _.NET Framework 4.7.1_. Following problems and suggestions were found:
Functionality problems
_Unsorted:_
8 (_Rename Folder_):
9 (_Duplicate_):
10 (_Import_). All problems are in _Port Scan_ functionality:
11 (_Export to file_)
_Acceptance testing_ guide
5 (_Save Connection File_ testing):
7 (_Delete_):
@PetbkA Great stuff here! I should have a little time tonight to start going through these notes. Thanks for helping with testing!
1.76.4.16229 - tested _View Menu_ section on _Windows 7 x64 SP1_ with _.NET Framework 4.7.1_. The results are:
_1 (Add Connection Panel)_
_7 (Jump To)_
_8 (Reset Layout)_
Also there's some "out-of-order" bugs concerning localization:
[x] Whenever themes are enabled or not (GIF):
[x] When themes are enabled, there are several bugs in Russian locale (GIF):
[x] Also in Russian locale there's English text in _Notification_, _Theme_ and _Security_ tabs, but I guess it's just lack of translation
Hotkeys for new folder and new connection stop working if File menu was called when PuTTy Saved Sessions was selected
Resolved under #999
Also it's possible to create new element inside PuTTy Saved Sessions - you have to create new folder in root element, then delete it - PuTTy node will be active (but, I guess, not focused), and it'll be possible to create new node inside it through hotkey.
Resolved under #998
@PetbkA I edited both your posts to add checkboxes to the issues you have raised. This will help me track which ones I've handled. Thanks again for your thorough testing, it is an immense help to getting 1.76 released.
@sparerd , thank you for the app :) Another "out-of-order" bug concerning _Connections tree panel_:
GIF that shows it. After this steps hotkeys stop working immediately. Bug doesn't reproduce if the left click will be on the other node or the right click will be done on the same node
1.76.4.16229 - tested _Tools_ and _Help_ menus section on _Windows 7 x64 SP1_ with _.NET Framework 4.7.1_:
Functionality problems
_Tools Menu_
No problems.
_Help Menu_
Acceptance testing guide issues
_Help Menu_
P.S.: I started to mark lists as checklists. Tell me if I shouldn't do so
What is considered the correct version? On the website I see Prerelease v1.76 Alpha 6, which doesn't equal to 1.76.4.16229. I suggest to use version from OS Uninstall or change a program window;
That is a fair point. I've been thinking about changing how we display the release versions on the website that is more indicative of the actual version number and also supports our update channels. (For example, 1.76.4.16229 could have been promoted to the beta update channel, which makes "v1.76 alpha 6" a very confusing label.) For this verification, it is probably enough to check that the About page version matches the version number shown when right clicking the app icon -> Properties -> Details -> Product version.
I think the value shown in the OS uninstall window can differ from the actual program version, depending on how the MSI was set up. Though this would probably be good to verify as well.
P.S.: I started to mark lists as checklists. Tell me if I shouldn't do so
Perfect! It will help me to not forgot things
2-5 (Websites). It's better to open links in default browser instead of mRNG tab that uses IE. Moreover, Report a Bug opens GitHub that says that browser is no longer supported;
This one will probably need to be moved out to v1.77 since it would be a larger change. There are a lot of unintuitive things that happen when connections are created (even going to a website). If you changed the browser engine set in the default connection info (must select Http/s protocol first) to Firefox, then the github message should go away.
But like you said, opening those sites in the default browser is probably the better way to go though.
Hotkeys stop working and disappear from the menu if I'll do the folowing steps:
- Right click on the node to call context menu;
- Left click on the same node to close menu.
GIF that shows it. After this steps hotkeys stop working immediately. Bug doesn't reproduce if the left click will be on the other node or the right click will be done on the same node
Resolved under #1001.
1.76.4.16229 - tested _Toolbars_ section on _Windows 10 LTSB 2016_ with _.NET Framework 4.7.1_. Also I'm using _vs2015dark_ theme and disable themes when I think that it might be the reason. The results are:
Functionality problems
Acceptance testing guide
1.76.4.16229 - tested _Button Menu_ and _Renaming tree items_ on _Windows 7 x64 SP1_ and _.NET Framework 4.7.1_:
Functionality problems
_Button Menu_
_Renaming tree items_
Acceptance guide
_Button Menu_
_Renaming tree items_
@PetbkA I went through some your port scan testing results.
Can't move through octets of IPs by arrows or Tab;
Noted - we will probably want to put in an enhancement request for this. It shouldn't been hard to add, but I'm not sure it's really a bug. Moving forward through octets can be done by using period (.), though there isn't a good way to move between start range/end range controls. Even the period key to move through octets doesn't seem like that great of a decision in hindsight. I'm not sure that all cultures use a period for octet separation. For example, German uses a comma for decimal number separation (1,25), do they use commas for octet separation too?
Also fixed the tab ordering between elements on this page to make it easier to fill out.
Stop button does nothing - Scan goes until completion;
Looks like the scan itself is done within 1-2 seconds for 255 hosts. The delay seen in the UI is due to huge inefficiencies in how the results are updated. The main issue seems to be that we try to update the UI for each individual ip result. The UI can't keep up and the update events queue up, leading to UI lock and unintuitive behavior of the "stop" scan button. By the time the UI is responsive, the scan has likely finished. We will want to rework this screen quite a bit to fix that.
Can't sort results;
Enhancement request: #841
Why Protocol to import is needed? If I'll choose RDP, it still imports only the selected node from the list, not all where RDP is available;
This controls the protocol assigned to the port scan results that are imported. Selecting "RDP" will import all selected scan results as connections with a protocol set to RDP. It does not control which results are imported. We may need to update the label text to be more clear about this - maybe "Protocol for imported connections:".
1.76.4.16229 - tested _Moving tree items_ section on _Windows 7 x64 SP1_ with _.NET Framework 4.7.1_:
No functionality problems.
Acceptance testing guide
Selecting "RDP" will import all selected scan results as connections with a protocol set to RDP
Strange logic. If I select 10 connections with _SSH_ protocol on half of them, what's the point of importing them as _RDP_ connections? IMHO importing only the connections that contain selected protocol is better
Strange logic. If I select 10 connections with SSH protocol on half of them, what's the point of importing them as RDP connections? IMHO importing only the connections that contain selected protocol is better
I think the reasoning was that while some ports may be well-known (3389, 22, 23, etc), a user may need to connect to a custom port (9260) for a protocol. But really I'm just guessing
I've just tried importing an rdg file from RDCman 2.7 and it gives the same error as 1.75 did.
These are the log entries:
2018-07-13 17:49:20,854 [1] ERROR - Unable to import file.
Exception has been thrown by the target of an invocation.
Object reference not set to an instance of an object.
@Vershner That appears to be trying to import, but having issues due to a bug. There is likely some field that we expected to find in the RDCman file that wasn't there. I've added some additional safety checks in the importer that should help. The next release will include the fix
2.iii. Caught an exception, presumably when I've choose connection from history and changed its type. I couldn't reproduce it.
Seems to be a weird case where the deletion target is null. I think c74f37f should fix this.
2.i. If something is entered in address field, changing protocol already opens connection. I guess that connection should start only when I press the button with protocol name;
This is working as originally designed, though I can see how this could be confusing. If it is problematic enough, we can open an issue to discuss it further.
If I choose single node and do the import through Import button at the lower right corner, Port Scan tab is closed. Reopening it crashes the app;
If I try to import several nodes through Import button at the lower right corner, I get unhandled exception immediately,
Resolved via #1030
If only one panel is opened, it can't be closed through x button. GIF that shows it.
That X button is actually to close a connection within the panel, not to close the panel itself. Since you don't have the "Always show panel tabs" option enabled and there is only one panel, you do not see the X button to close the panel. This should be less confusing when we remove one of the two windowing libraries that we are using (#155). Also slightly related to the conversation in #368.
Switching language still leaves some interface elements from home locale. In my case Russian text is present in context menus when English locale is enabled
I was able to find a fix for this. We were setting the language of the connection context menu before loading the culture/language that should be used. Resolved under #1034
When app is started with russian locale, opening Options switches menu toolbar (but none of it's sections contents) to English;
This one has me stumped. I can replicate the issue, but I can't seem to find how this is happening or why. The menu text changes during a system level WndProc() call, but I'm not seeing any C# code that could be causing it. This one may take a bit to track down. Created #1037 to track this bug
If Options window is closed on Connections tab, opening Options again causes unhandled exception
Resolved under #1036
Standard regression testing is done for v1.76