Testing topics (some ideas)

[GoogleCodeExporter]

1. Create project from scratch, parse and create derivatives with
branding/banding. 

2. Deleting projects under various options

3. Import existing data into project. 

4. Export data from project.

5. Creating, exporting, and importing controlled vocabulary and tying it to
data.

6. Functionality of various field options ('large', 'multiple', 'date' etc)

7. Auto log out and notification

8. Auto save(?)

9. User creation, deletion, editing. 

10. Permission settings for users.

11. Searching function

12. View Metadata functionality

13. "These" and "New" options for parser

14. Parser correctly deletes old derivatives 

15. File naming.

16. Input Validation functionality (eg. what happens if bad input is given?)

Original issue reported on code.google.com by haruki.y...@gmail.com on 23 Jan 2010 at 6:25

[GoogleCodeExporter]

Original comment by haruki.y...@gmail.com on 29 Jan 2010 at 9:49

• Added labels: Milestone-Ongoing

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Something I ripped off the web

1) Functionality Testing
2) Usability testing
3) Compatibility testing
4) Security testing

1) Functionality Testing:

Test for - all the links in web pages, database connection, Cookie testing.

Database testing:
Data consistency is very important in web application. Check for data integrity 
and
errors while you edit, delete, modify the forms or do any DB related 
functionality.
Check if all the database queries are executing correctly, data is retrieved
correctly and also updated correctly.

2) Usability Testing:

Test for navigation:
Navigation means how the user surfs the web pages, different controls like 
buttons,
boxes or how user using the links on the pages to surf different pages.
Usability testing includes:
Web site should be easy to use. Instructions should be provided clearly. Check 
if the
provided instructions are correct means whether they satisfy purpose.

3) Compatibility Testing:
Compatibility of your web site is very important testing aspect. See which
compatibility test to be executed:

    * Browser compatibility
    * Operating system compatibility
    * Printing options
checked for software, hardware memory leakage errors,

4) Security Testing:

Following are some test cases for web security testing:

    * Test by pasting internal url directly into browser address bar without login.
Internal pages should not open.

    * Try some invalid inputs in input fields like login username, password, input
text boxes. Check the system reaction on all invalid inputs.

    * Web directories or files should not be accessible directly 

Original comment by haruki.y...@gmail.com on 5 Feb 2010 at 7:24

[GoogleCodeExporter]

hmm OS compatibility is not a prob but browser compatibility is. JVM also 
handles its
own memory so leakage is not really possible and we cannot detect it anyway.

Original comment by long...@gmail.com on 6 Feb 2010 at 9:55

[GoogleCodeExporter]

Original comment by haruki.y...@gmail.com on 5 May 2010 at 5:24

• Added labels: Time-Ongoing

[GoogleCodeExporter]

I accessed from Japan and it's pretty fast, actually. Fairly decent even in 
Safari. Windows XP + IE 6(?) was a no go

Original comment by haruki.y...@gmail.com on 2 Aug 2010 at 1:31