Changes between Initial Version and Version 3 of Ticket #1746


Ignore:
Timestamp:
Jan 14, 2008, 8:36:37 AM (13 years ago)
Author:
Thilo Schwarz
Comment:

Replying to fredck:

This is quite a difficult thing to handle in JUnit, as the test code also needs to identify the browser with a code that is basically similar to the code used in FCKeditor.Java for the browser check.

The only possible automation would be testing the compatibility checks over a list of browser user agent strings, which means that the check code should be separated from the user agent string retrieval code.

That's exactly what I want to do! I don't want to check the agent string retrieval code.

My Compatibility class gets only one argument, the user agent string. And so it is possible to check this class over a list of browser agent strings, as you said. So we can ensure, that the compatibility check works as it expected for a list of user agent strings. And that would be very helpful!

Do you have some exemplary user agent strings, for negative and positive checks? Otherwise I'll take some from http://www.zytrax.com/tech/web/browser_ids.htm.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1746

    • Property Status changed from new to assigned
    • Property Summary changed from Implement JUnit tests for browser compatibilty check to Implement JUnit tests for browser compatibility check
  • Ticket #1746 – Description

    initial v3  
    1 We need some exemplary JUnit tests for the class Compatibility to ensure, the browser compatibiltiy check works fine.
     1We need some exemplary JUnit tests for the class Compatibility to ensure, the browser compatibilitiy check works fine.
© 2003 – 2020 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy