Originally Posted by
travel.flier
couldn't agree more. we are definitely the best beta testers. but also savvy enough not to pay money to be a beta tester.
Yeah, we don't pay to use Marriott's web site (other than our waste of time) and we are still beta testing that POS. Every time they make a change it is for the worse. The latest is when searching for reservations, now when you click on a hotel's name you get a java pop up. Oh cool - NOT. To get to the web site you have to click two links now, the hotel name which gives the java pop up and then the link that says go to the hotel web site. Not an improvement IMO.
To the OP: Good luck with your endeavor. I suggest you do more work on your product, get the functionality and associated bugs flushed out, regression test it yourself, and then reintroduce it. It doesn't sound like it is ready for prime time, but then again Marriott.com isn't either but they aren't asking us to pay for it.
Pay particular attention to entry using soft tools (embedded calendars) and manual entries, taking into account the top 4 browsers (IE, FF, Chrome and Safari) and associated caching/autofill features, common logic edits like date congruency, enter a state, USA is prefilled, enter a province, CA is prefilled, etc. What happens when someone enters (or selects - you need to test BOTH) a date in the Arrival field, the departure field should be prefilled with the date of the next day (something that Marriott failed to do in their update a number of months ago, nor fix after numerous complaints). From these posts, it sounds as though you have looked at functionality given valid input but neglected actually performing thorough editing of that input and providing appropriate error processing and messages.