Announcement

Collapse
No announcement yet.

Evaluation of Webaccess Testlog 3.0 Build 1025

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Evaluation of Webaccess Testlog 3.0 Build 1025

    I have evaluated Web based testlog. My findings are as under:

    1) User is not able to edit any already existing project.

    2) User is in a particular project, and under this project he is
    trying to create "New Test Suite". User enters the name in text field and selects <create> button. The application is giving an error message. When user selects <Back> button on this screen and again selects the <Create> button (i.e.. on "Test Suite Creation" screen), an error message appears, which informs about the duplication of test suite. "Could not create test case, one with the same name already exists"

    3) User is able to create "new test case" without creation of test suite.
    Steps- Select a project-Select the tab for "New project test suite "-On this page select the tab for "New project test case-Create new test case and save it.

    4) User is not able to edit name of already existing test suites/ test
    cases

    5) After we enter a project, the application should give list of test
    suites instead of test cases.

    6) User is not able to edit "Title" "Description" and content of already
    existing test suites.

    7) While creating new test case, the "Author" and "Update By" fields
    accepts the tester names. Here the entry can be allowed by using drop down menu (i.e.. Drop down containing list of testers)

    While creating new test case, the "Test Updated Time & Last Updated
    Date" and "Test Creation Time & Test Creation Date" fields accepts manual entry. It can be by having proper "Calendar" control button and proper "Time" entry button objects.

    9) While creating new test case, the "Priority" field is having default
    value of "Highest". It can be "Medium".

    10) While creating new test case, the field "External Description Link"
    and "External Result Link" are not having any "Browse button" or any "Launch button". They can have these buttons.

    11) In EDIT mode of test case, when BACK button is pressed, without ‘cancelling edit’ or ‘saving’ it, then it goes in loop.

    12) While creating new test case, the "Number of Test Attempts" field can have default value of zero.

    13) While creating/editing a test case, if user enters large data in any text field; the application gives an error message "CGI Error: The specified CGI application misbehaved by not returning a complete set of HTTP headers".

    14) When user creates new test case without filling the field "Expected Test Duration" and saves it, an error message "Invalid time specified for Expected Test Duration (HHH:MM) Please use your back button to return to the edit form and correct the time." appears.

    15) When user navigates as Home » <database> » Test Cases and creates new test case, the fields "Expected Test Duration (HHH:MM) " "Actual Test Duration (HHH:MM) " appears empty. but if user navigates as Home » <database> » Projects »Test Cases, then these fields are having default value of zero.

    16) On creation of a new test suite, only ‘New test suite name’ is asked.
    It can also ask for ‘Test suite Id’.

    17) While creating a test suite if ‘New test suite name’ field is left blank and ‘Create’ button is clicked then error message "Could not create test suite, one with same name already exists" appears.

  • #2
    Thanks for your post. It is Friday afternoon here, and it is a long post. So we won't be able to fully address it until next week.

    I think some of the points are normal behaviour and some of the issues are just a result of the web interface not being as functional as the desktop interface. The web interface was not designed as a complete replacement for the desktop interface.

    But we have a look at each item and work out which ones are bugs next week.

    Comment


    • #3
      1,4,6,7,9 are limitations of the web version, as it is a lightweight version of desktop version of TestLog we haven't been able to implement every feature available. We are planning to continue development of the web version and add more functionality.

      8,10, Require embedded JavaScript controls so we'll keep them in mind for a future version.

      2, does the user have read only permissions instead of read/write? Currently there is no create permission, so anyone can create a new test suite but if they don't have write permission they can't edit the newly created suite. The next release is likely to have a third level of permissions for read/write/create.

      11, we weren't able to reproduce/see what you mean, clicking back displays the screen previous to the edit.

      13, we weren't able to reproduce this, how much data were you entering and from what sort of source (eg pasting from a word doc etc)?

      16, currently the test case is created before being opened for editing, otherwise if the test case couldn't be created due to a naming conflict there was the possibility that the entered data for all the other fields could be lost.

      3,5,12,14,15,17 will be fixed for the next release.

      Comment


      • #4
        Evaluation of Webaccess Testlog 3.0 Build 1025

        Hi Tim

        Thanks for reply!

        When is next release of web version expected? We might need to evaluate next release and implement it at client site if possible.

        Regards,
        Sandeep Sharma

        Comment


        • #5
          If will probably be 2-3 weeks before we can release a new build with the bug fixes.

          Comment

          Working...
          X