-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document for manual testing of GUI #1215
Comments
@aashish24 @doutriaux1 I am about to finish this document. I have tested all the plots present in UVCDAT. I need your help to write description of each plot present in our application. Just a line or two about what these plots and subcategories does. Like what is Isofill and what is a_robinson_isofill under isofill. My intention is that, this document could work as a guide for new users of UVCDAT in some way. |
Hello, This is the initial draft of the document user or developer can use for testing UVCDAT GUI. |
thanks @vvpalav that is very nice! Is there any way we could make this more edit friendly, like put it on some wiki or something? |
well I was looking for similar option, but I created document locally in my machine. Why don't you download the document and edit it in your machine. Just highlight the changes and send it back to me at vv221@nyu.edu. I will merge changes from everyone and publish final document. |
What I don't like about this is that it unnecessarily increases the size of the repo and it is harder to see what changed between version. But I will do like this for now. |
Thats an interesting point. Well lets make the changes offline for now and publish 1.0 version. meanwhile I will try to find out if we can upload it somewhere online so that we can track changes and everyone can edit the same document. @williams13 @potter2 @aashish24 @remram44 .. will you please take a look at the document and suggest anything that needs to be add/modify/remove from the doc. There are couple of sections in the doc where I was not sure how those works, like visualization properties, diagnostics, animation, climate data tools etc. we need to complete this sections. My main intention with this document is to make it a one stop solution for brief testing and a guide for the UVCDAT GUI for new comers or existing developers and users. |
I have also posted a document containing all the issues/suggestions I come across while testing GUI. we need to confirm if this issues are valid and then we can start fixing them for 2.3 |
@vvpalav as far as explaining each a_isofill etc... I think it is worth mentioning that any customized graphic method that the user saves to it's initial.attribute will show up here, so this window can potentially look different for every users (especially ones that have been using UV-CDAT for a while). |
@doutriaux1 I am going to create Wiki Page named "Manual Testing of UVCDAT using GUI" and put the content of the document inside it. As I said earlier, I think there are still some parts where we need inputs from other users. I'll let you know once page is ready. |
@hgohil2805 is checking whether we can automatically test this scenario using a tool like Sikuli -- the idea would be to update both the scenario on the wiki page and the Sikuli script as new features are added |
Just created a wiki page Manual Testing of UVCDAT using GUI. Link is also present on UVCDAT wiki under Documentation and Tutorials as Manual Testing of UVCDAT using GUI. Please review this and let me know. |
This is awesome! Thanks for putting this together! |
This issue is to create documentation for manual testing of UVCDAT gui before release.
Reference: #1214
The text was updated successfully, but these errors were encountered: