Re: [Fofredux-devel] Updated files?

[Kevin <ke...@dr...>]

> Well, I was still dealing w/ my annoying and unreproducable problem.
> I'm willing to put forth that it's something weird in my system/setup
> that I'm somehow not catching, if no one else sees that problem.
>
> I actually just caught a bug dealing w/ what files from Head were
> moved up to 0.3 and not. Init.php had an update to how it parsed opml
> files, but add.php wasn't migrated to the 0.3 tag as well which
> handled these changes. Therefore, importing an OPML file would always
> fail. This was a shortcoming on my part to mark which files should
> move forward. What do we do in the future to mark files on HEAD that
> need to be moved to a new RC?

In subversion, which I hope we are migrated to before the next release,=20
each tag is a complete copy of trunk.  This will hopefully eliminate the
problem of mismatched file tags.

In general, I don't like the idea of moving tags.  If you want to update =
a
release candidate, then that is a new RC tag.  RC2-0_3, etc.  What you ar=
e
doing with the RC tag should be accomplished with a branch.

> Here are the prescribed tests for future releases.
> Install:
> 1) Install new from scratch
> 2) Upgrade System from previous version (at least previous, further
> back is good too)
> 3) Uninstall
>
> Setup
> 1) Add single feed of type: RSS 0.92, RSS 1.0, RSS 2.0, Atom
> 2) Add feed of html page that uses auto-discovery
> 3) Add invalid feed (html page, non-existing page, etc.) and verify
> error message
> 4) Add categories
> 5) Add feeds with selected categories
> 6) Export OPML file - verify that url, name, categories are written
> for all feed items
> 7) Import OPML file (with and without categories)
>
> Panel:
> 1) Edit a feed, change category, url, name, location, tags,
> auto-update & verify these changes took effect
> 2) Edit a category - verify change took effect
> 3) Delete a category- make sure feeds of that category changed to "None=
"
> 4) Set options for number of feeds, server time offset, etc.
> 5) Create and remove tags
>
> View (both full page and framed):
> 1) Verify all buttons in menu work as expected: e.g.
>  2) View new items - verify they are paged, in the correct order, only
> unread items are shown
>  3) View all items
>  4) View category
>  5) View individual feed
> 6) Tag an item, remove the tag
> 7) Save an item, view saved feeds, unsave item
> 8) Mark an item as read, verify it doesn't show up in new
> 9) View all items, and mark items as unread - verify they show up in "n=
ew
> items"
> 10) View feeds by a tag
> 11) Use "flag up to" to mark items as read
> 12) Mark all items as read/unread
> 13) Verify that all other links in a feed item work (name, category,
> in-item links)
> 14) view "Old to new" and "new to old"
>
> Other:
> 1) Search from the panel - all feeds should be searched
> 2) Search within a view, only feeds in that view should be searched
> 3) "Previous" and "next" within a search stays within a search


Looks good, how much of this can be accomplished with test cases, do you
think?  Anything that touches an init.php function, should be a candidate
for automatic testing.


> Ok - I think that covers things in a rough way. I've tested most of
> these (as I wrote them), There were several bugs in passing the order
> and paging through the various nav links. These have been fixed and
> tagged to RC-0_3. In fact, the keeping of parameters from one view to
> the next seems odd, as *all* possible parameters will show up even if
> they don't have values. This should be addressed in the next version.

I've thought of the idea of encapsulating all parameters that make up an
item view into an object.(tags, feeds, categories, search term, flag, etc=
)
 That way, functions like fof_get_items() would be passed one parameter
instead of 8.  That said.  It would be the item_view object's job to
marshall/unmarshall query parameters for links.  The item_view object
would also represent a saveable search.


> I feel good about the release now and think we should go ahead and
> bundle it up and SHIP!
>
> Let me know if anyone has any immediate issues, or gives the thumbs up =
to
> v0.3

Yipee!!

--=20
Kevin