Bedework Testing for 3.6 Release

This page documents the features to be tested Bedework for the 3.6 release. Real bugs will be entered in Trac.

URL and Widget Builder

(Done)

• dynamic page elements
  • click widget choice. Should output type and URL, and reveals widget options and the widget code box.
    • on Show a title above event list? click False. Title box should close.
    • click True. Title box should open.
    • on Display event details inline? click True. More options should appear.
    • click False. The opens below should disappear.
  • click feed choice. Make sure everything reverses.
  • click Include selected categories only. List of categories should open up.
  • click Include everything. Category list should close up.
  • click Exclude selected categories. List of categories should open up.
  • click Nothing to exclude. Category list should close up.
  • click Limit to an organization. Org Category list should open up.
  • click No limit. List should close up.

• URL rewrites and date widgets
  • click on feed. Click on each output type.
    • make sure that when ics is chosen that the skin path element disappears.
    • make sure that when you click off ics a skin path element reappears
  • slider make sure that slider works and that the number corresponds to the url element
  • date range: click radio next to date range
    • the first element of the url should change from <outputlang>days to <outputlang>range
    • the days number should be replaced by a pair of elements, each with 8 zeros.
    • click on the start date widget and make sure it comes up.
    • choose a start date and see if it replaces the first set of zeros. It should be yyyymmdd.
    • click on the end date widget and make sure it comes up.
    • choose an end date and see if it replaces the second set of zeros. It should be yyyymmdd.
  • go back to the top and click on widget.
    • for true/false options, try both positions and make sure the option in the widget code box changes.
    • type something in the title box and make sure it appears.
  • Categories. Because of the encoding, it's hard to verify, but....
    • Make sure as you click on and off included categories, the filter expression grows and shrinks in length
    • Make sure as you click on and off excluded categories, the filter expression grows and shrinks in length
    • Make sure as you click on and off a limit, the filter expression grows and shrinks in length

Widget

(Done)

Making sure you have a few events, then paste the widget code in an HTML test page. Make sure the data looks right. After that, you can use the test case in the project that points to local data. Put it in an editor and change the true/false choices and the title.

• Show default title
• Show my title
• Don't show title
• Highlight date
• Highlight title
• Display time
• Display location
• Display Details
  • Display contact
  • Display cost
  • Display tags
  • Display timezone

CachedFeeder

(Still Testing)

You can certainly test output, but another good way to test the cache is to check the Bedework URLs that the cache generates for each request. These are spit out in the server's log. Watch for log entries that start with "[java] INFO: URL is ". It's also good to watch the log to discover when the webserver is serving the cached page directly rather than calling Bedework to fetch the data and render the results.

Items to concentrate on

• filter expressions (fexpr in the bedework URL)
• json object comes and goes depending on that cache URL segment