You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Richard Hirsch <hi...@gmail.com> on 2011/03/01 09:14:42 UTC
Rel 1.2 RC2 tests
Hi,.
I'm currently testing the stax deplyoment.
I'll be testing each day a little bit.
Instead of random tests, I'm trying to test the complete functionality
as good as possible.
I'll be documenting my tests, so other community members know what has
been tested.
Others should document their tests as well, so that we have a basic
release test plan that we can use for future releases:
D.
---------------------
Browser Chrome
1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
in a incognito window
2. Create new user via sign-up page
3. Created message "Test #Retz @h" from main page
4. Clicked @h link
5. Page to main page via "Home" link
6. Clicked on #Retz link
7. Clicked on "test12rc2"
8. Clicked on "Streams" page
9. Created message "Streams message"
10. Returned to main page via click on ESME icon
11. Clicked on public link
12. Clicked on "My Profile" link
13. Changed first name, last name
14. Clicked on "My Tracks"
15. Added Track for "Frog"
16. Opened ESME in another browser (IE) with another user
17. Added message "Frog track test"
18. Checked in Chrome whether message from IE user appears
19. Set Frog track to "inactive"
20. In IE - added new message "Frog track test-inactive"
21. Check in Chrome whether message "Frog track test-inactive" appears
22. Delete track "Frog"
20. In IE - added new message "Frog track test-deleted"
21. Check in Chrome whether message "Frog track test-deleted" appears
22. Added Track for "Frog"
20. In IE - added new message "Frog track in pool" in a pool in which
the Chrome user is not a member
21. In IE added Chrome user to the pool
22. In IE - added new message "Frog in pool with Chrome user included"
in a pool in which the Chrome user is a member
Re: Rel 1.2 RC2 tests
Posted by Richard Hirsch <hi...@gmail.com>.
The null tag is from the old IE JS error - I also noticed it.
Creating the release now - I always forget how to do this - we need to
release more often. ;->
D.
On Fri, Mar 4, 2011 at 4:52 PM, Ethan Jewett <es...@gmail.com> wrote:
> Interesting. Following tags seems to work for me. Though I did just
> realize that there is something weird going on with the Null tag. Is
> someone doing something crazy with the API?
>
> In any case, I agree, no show-stoppers as far as I can tell. Thanks
> for starting the release process!
>
> Ethan
>
> On Fri, Mar 4, 2011 at 4:21 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> Just finished my tests -- had a strange error on following a tag but
>> it shouldn't stop the release.
>>
>> I also found a few other issues that I will be adding to 1.3 issue list.
>>
>> I'm now starting the 1.2 release process
>>
>> D.
>>
>> ------------
>>
>> 1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
>> in a incognito window
>> 2. Create new user via sign-up page
>> 3. Created message "Test #Retz @h" from main page
>> 4. Clicked @h link
>> 5. Page to main page via "Home" link
>> 6. Clicked on #Retz link
>> 7. Clicked on "test12rc2"
>> 8. Clicked on "Streams" page
>> 9. Created message "Streams message"
>> 10. Returned to main page via click on ESME icon
>> 11. Clicked on public link
>> 12. Clicked on "My Profile" link
>> 13. Changed first name, last name
>> 14. Clicked on "My Tracks"
>> 15. Added Track for "Frog"
>> 16. Opened ESME in another browser (IE) with another user
>> 17. Added message "Frog track test"
>> 18. Checked in Chrome whether message from IE user appears
>> 19. Set Frog track to "inactive"
>> 20. In IE - added new message "Frog track test-inactive"
>> 21. Check in Chrome whether message "Frog track test-inactive" appears
>> 22. Delete track "Frog"
>> 20. In IE - added new message "Frog track test-deleted"
>> 21. Check in Chrome whether message "Frog track test-deleted" appears
>> 22. Added Track for "Frog"
>> 20. In IE - added new message "Frog track in pool" in a pool in which
>> the Chrome user is not a member
>> 21. In IE added Chrome user to the pool as reader
>> 22. In IE - added new message "Frog in pool with Chrome user included"
>> in a pool in which the Chrome user is a member
>> -----
>> 23. In Chrome - user can't post to pool but can post
>> 24. Change Chrome user to have write privileges to pool
>> 25. Chrome user should be able to post to pool
>> 26. IE user resends a message and after browser refresh in Chrome - no
>> message appears in Popular Messages category
>> 27. User in Chrome follows user in IE
>> 29. IE user resends a message and after browser refresh in Chrome -
>> message appears in Popular Messages category
>> 30. In Chrome - the IE user now appears in "My Contacts"
>> 31. User in Chrome unfollows user in IE
>> 32. In Chrome - the IE user no longer appears in "My Contacts"
>> 33. user in IE follows user in Chrome
>> 34. After page refresh in IE, Chrome user now appears in IE User's
>> MyContacts page
>> 35. IE user appears in Chrome user 'Followers Tab in "My Contacts" Page
>> 36. Chrome user follow tag #Retz on Tag page
>> 37. Chrome user unfollows IE user
>> 38. IE user creates message "test #Retz"
>> 39. Chrome user should get the message "test #Retz" from IE user
>> despite the fact that he/she isn't following the user : error
>>
>> On Thu, Mar 3, 2011 at 8:45 AM, Ethan Jewett <es...@gmail.com> wrote:
>>> Sounds good. I've been using Stax a little bit every day and I haven't
>>> noticed anything amiss aside from the small bug I filed in the
>>> backlog.
>>>
>>> Ethan
>>>
>>> On Thursday, March 3, 2011, Richard Hirsch <hi...@gmail.com> wrote:
>>>> I'm going to continue my tests today and then I'll cut a 1.2 release
>>>> either tomorrow or Monday.
>>>>
>>>> D.
>>>>
>>>> On Tue, Mar 1, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>> Hi,.
>>>>>
>>>>> I'm currently testing the stax deplyoment.
>>>>>
>>>>> I'll be testing each day a little bit.
>>>>>
>>>>> Instead of random tests, I'm trying to test the complete functionality
>>>>> as good as possible.
>>>>>
>>>>> I'll be documenting my tests, so other community members know what has
>>>>> been tested.
>>>>>
>>>>> Others should document their tests as well, so that we have a basic
>>>>> release test plan that we can use for future releases:
>>>>>
>>>>> D.
>>>>>
>>>>> ---------------------
>>>>> Browser Chrome
>>>>>
>>>>> 1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
>>>>> in a incognito window
>>>>> 2. Create new user via sign-up page
>>>>> 3. Created message "Test #Retz @h" from main page
>>>>> 4. Clicked @h link
>>>>> 5. Page to main page via "Home" link
>>>>> 6. Clicked on #Retz link
>>>>> 7. Clicked on "test12rc2"
>>>>> 8. Clicked on "Streams" page
>>>>> 9. Created message "Streams message"
>>>>> 10. Returned to main page via click on ESME icon
>>>>> 11. Clicked on public link
>>>>> 12. Clicked on "My Profile" link
>>>>> 13. Changed first name, last name
>>>>> 14. Clicked on "My Tracks"
>>>>> 15. Added Track for "Frog"
>>>>> 16. Opened ESME in another browser (IE) with another user
>>>>> 17. Added message "Frog track test"
>>>>> 18. Checked in Chrome whether message from IE user appears
>>>>> 19. Set Frog track to "inactive"
>>>>> 20. In IE - added new message "Frog track test-inactive"
>>>>> 21. Check in Chrome whether message "Frog track test-inactive" appears
>>>>> 22. Delete track "Frog"
>>>>> 20. In IE - added new message "Frog track test-deleted"
>>>>> 21. Check in Chrome whether message "Frog track test-deleted" appears
>>>>> 22. Added Track for "Frog"
>>>>> 20. In IE - added new message "Frog track in pool" in a pool in which
>>>>> the Chrome user is not a member
>>>>> 21. In IE added Chrome user to the pool
>>>>> 22. In IE - added new message "Frog in pool with Chrome user included"
>>>>> in a pool in which the Chrome user is a member
>>>>>
>>>>
>>>
>>
>
Re: Rel 1.2 RC2 tests
Posted by Ethan Jewett <es...@gmail.com>.
Interesting. Following tags seems to work for me. Though I did just
realize that there is something weird going on with the Null tag. Is
someone doing something crazy with the API?
In any case, I agree, no show-stoppers as far as I can tell. Thanks
for starting the release process!
Ethan
On Fri, Mar 4, 2011 at 4:21 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Just finished my tests -- had a strange error on following a tag but
> it shouldn't stop the release.
>
> I also found a few other issues that I will be adding to 1.3 issue list.
>
> I'm now starting the 1.2 release process
>
> D.
>
> ------------
>
> 1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
> in a incognito window
> 2. Create new user via sign-up page
> 3. Created message "Test #Retz @h" from main page
> 4. Clicked @h link
> 5. Page to main page via "Home" link
> 6. Clicked on #Retz link
> 7. Clicked on "test12rc2"
> 8. Clicked on "Streams" page
> 9. Created message "Streams message"
> 10. Returned to main page via click on ESME icon
> 11. Clicked on public link
> 12. Clicked on "My Profile" link
> 13. Changed first name, last name
> 14. Clicked on "My Tracks"
> 15. Added Track for "Frog"
> 16. Opened ESME in another browser (IE) with another user
> 17. Added message "Frog track test"
> 18. Checked in Chrome whether message from IE user appears
> 19. Set Frog track to "inactive"
> 20. In IE - added new message "Frog track test-inactive"
> 21. Check in Chrome whether message "Frog track test-inactive" appears
> 22. Delete track "Frog"
> 20. In IE - added new message "Frog track test-deleted"
> 21. Check in Chrome whether message "Frog track test-deleted" appears
> 22. Added Track for "Frog"
> 20. In IE - added new message "Frog track in pool" in a pool in which
> the Chrome user is not a member
> 21. In IE added Chrome user to the pool as reader
> 22. In IE - added new message "Frog in pool with Chrome user included"
> in a pool in which the Chrome user is a member
> -----
> 23. In Chrome - user can't post to pool but can post
> 24. Change Chrome user to have write privileges to pool
> 25. Chrome user should be able to post to pool
> 26. IE user resends a message and after browser refresh in Chrome - no
> message appears in Popular Messages category
> 27. User in Chrome follows user in IE
> 29. IE user resends a message and after browser refresh in Chrome -
> message appears in Popular Messages category
> 30. In Chrome - the IE user now appears in "My Contacts"
> 31. User in Chrome unfollows user in IE
> 32. In Chrome - the IE user no longer appears in "My Contacts"
> 33. user in IE follows user in Chrome
> 34. After page refresh in IE, Chrome user now appears in IE User's
> MyContacts page
> 35. IE user appears in Chrome user 'Followers Tab in "My Contacts" Page
> 36. Chrome user follow tag #Retz on Tag page
> 37. Chrome user unfollows IE user
> 38. IE user creates message "test #Retz"
> 39. Chrome user should get the message "test #Retz" from IE user
> despite the fact that he/she isn't following the user : error
>
> On Thu, Mar 3, 2011 at 8:45 AM, Ethan Jewett <es...@gmail.com> wrote:
>> Sounds good. I've been using Stax a little bit every day and I haven't
>> noticed anything amiss aside from the small bug I filed in the
>> backlog.
>>
>> Ethan
>>
>> On Thursday, March 3, 2011, Richard Hirsch <hi...@gmail.com> wrote:
>>> I'm going to continue my tests today and then I'll cut a 1.2 release
>>> either tomorrow or Monday.
>>>
>>> D.
>>>
>>> On Tue, Mar 1, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> Hi,.
>>>>
>>>> I'm currently testing the stax deplyoment.
>>>>
>>>> I'll be testing each day a little bit.
>>>>
>>>> Instead of random tests, I'm trying to test the complete functionality
>>>> as good as possible.
>>>>
>>>> I'll be documenting my tests, so other community members know what has
>>>> been tested.
>>>>
>>>> Others should document their tests as well, so that we have a basic
>>>> release test plan that we can use for future releases:
>>>>
>>>> D.
>>>>
>>>> ---------------------
>>>> Browser Chrome
>>>>
>>>> 1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
>>>> in a incognito window
>>>> 2. Create new user via sign-up page
>>>> 3. Created message "Test #Retz @h" from main page
>>>> 4. Clicked @h link
>>>> 5. Page to main page via "Home" link
>>>> 6. Clicked on #Retz link
>>>> 7. Clicked on "test12rc2"
>>>> 8. Clicked on "Streams" page
>>>> 9. Created message "Streams message"
>>>> 10. Returned to main page via click on ESME icon
>>>> 11. Clicked on public link
>>>> 12. Clicked on "My Profile" link
>>>> 13. Changed first name, last name
>>>> 14. Clicked on "My Tracks"
>>>> 15. Added Track for "Frog"
>>>> 16. Opened ESME in another browser (IE) with another user
>>>> 17. Added message "Frog track test"
>>>> 18. Checked in Chrome whether message from IE user appears
>>>> 19. Set Frog track to "inactive"
>>>> 20. In IE - added new message "Frog track test-inactive"
>>>> 21. Check in Chrome whether message "Frog track test-inactive" appears
>>>> 22. Delete track "Frog"
>>>> 20. In IE - added new message "Frog track test-deleted"
>>>> 21. Check in Chrome whether message "Frog track test-deleted" appears
>>>> 22. Added Track for "Frog"
>>>> 20. In IE - added new message "Frog track in pool" in a pool in which
>>>> the Chrome user is not a member
>>>> 21. In IE added Chrome user to the pool
>>>> 22. In IE - added new message "Frog in pool with Chrome user included"
>>>> in a pool in which the Chrome user is a member
>>>>
>>>
>>
>
Re: Rel 1.2 RC2 tests
Posted by Richard Hirsch <hi...@gmail.com>.
Just finished my tests -- had a strange error on following a tag but
it shouldn't stop the release.
I also found a few other issues that I will be adding to 1.3 issue list.
I'm now starting the 1.2 release process
D.
------------
1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
in a incognito window
2. Create new user via sign-up page
3. Created message "Test #Retz @h" from main page
4. Clicked @h link
5. Page to main page via "Home" link
6. Clicked on #Retz link
7. Clicked on "test12rc2"
8. Clicked on "Streams" page
9. Created message "Streams message"
10. Returned to main page via click on ESME icon
11. Clicked on public link
12. Clicked on "My Profile" link
13. Changed first name, last name
14. Clicked on "My Tracks"
15. Added Track for "Frog"
16. Opened ESME in another browser (IE) with another user
17. Added message "Frog track test"
18. Checked in Chrome whether message from IE user appears
19. Set Frog track to "inactive"
20. In IE - added new message "Frog track test-inactive"
21. Check in Chrome whether message "Frog track test-inactive" appears
22. Delete track "Frog"
20. In IE - added new message "Frog track test-deleted"
21. Check in Chrome whether message "Frog track test-deleted" appears
22. Added Track for "Frog"
20. In IE - added new message "Frog track in pool" in a pool in which
the Chrome user is not a member
21. In IE added Chrome user to the pool as reader
22. In IE - added new message "Frog in pool with Chrome user included"
in a pool in which the Chrome user is a member
-----
23. In Chrome - user can't post to pool but can post
24. Change Chrome user to have write privileges to pool
25. Chrome user should be able to post to pool
26. IE user resends a message and after browser refresh in Chrome - no
message appears in Popular Messages category
27. User in Chrome follows user in IE
29. IE user resends a message and after browser refresh in Chrome -
message appears in Popular Messages category
30. In Chrome - the IE user now appears in "My Contacts"
31. User in Chrome unfollows user in IE
32. In Chrome - the IE user no longer appears in "My Contacts"
33. user in IE follows user in Chrome
34. After page refresh in IE, Chrome user now appears in IE User's
MyContacts page
35. IE user appears in Chrome user 'Followers Tab in "My Contacts" Page
36. Chrome user follow tag #Retz on Tag page
37. Chrome user unfollows IE user
38. IE user creates message "test #Retz"
39. Chrome user should get the message "test #Retz" from IE user
despite the fact that he/she isn't following the user : error
On Thu, Mar 3, 2011 at 8:45 AM, Ethan Jewett <es...@gmail.com> wrote:
> Sounds good. I've been using Stax a little bit every day and I haven't
> noticed anything amiss aside from the small bug I filed in the
> backlog.
>
> Ethan
>
> On Thursday, March 3, 2011, Richard Hirsch <hi...@gmail.com> wrote:
>> I'm going to continue my tests today and then I'll cut a 1.2 release
>> either tomorrow or Monday.
>>
>> D.
>>
>> On Tue, Mar 1, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>> Hi,.
>>>
>>> I'm currently testing the stax deplyoment.
>>>
>>> I'll be testing each day a little bit.
>>>
>>> Instead of random tests, I'm trying to test the complete functionality
>>> as good as possible.
>>>
>>> I'll be documenting my tests, so other community members know what has
>>> been tested.
>>>
>>> Others should document their tests as well, so that we have a basic
>>> release test plan that we can use for future releases:
>>>
>>> D.
>>>
>>> ---------------------
>>> Browser Chrome
>>>
>>> 1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
>>> in a incognito window
>>> 2. Create new user via sign-up page
>>> 3. Created message "Test #Retz @h" from main page
>>> 4. Clicked @h link
>>> 5. Page to main page via "Home" link
>>> 6. Clicked on #Retz link
>>> 7. Clicked on "test12rc2"
>>> 8. Clicked on "Streams" page
>>> 9. Created message "Streams message"
>>> 10. Returned to main page via click on ESME icon
>>> 11. Clicked on public link
>>> 12. Clicked on "My Profile" link
>>> 13. Changed first name, last name
>>> 14. Clicked on "My Tracks"
>>> 15. Added Track for "Frog"
>>> 16. Opened ESME in another browser (IE) with another user
>>> 17. Added message "Frog track test"
>>> 18. Checked in Chrome whether message from IE user appears
>>> 19. Set Frog track to "inactive"
>>> 20. In IE - added new message "Frog track test-inactive"
>>> 21. Check in Chrome whether message "Frog track test-inactive" appears
>>> 22. Delete track "Frog"
>>> 20. In IE - added new message "Frog track test-deleted"
>>> 21. Check in Chrome whether message "Frog track test-deleted" appears
>>> 22. Added Track for "Frog"
>>> 20. In IE - added new message "Frog track in pool" in a pool in which
>>> the Chrome user is not a member
>>> 21. In IE added Chrome user to the pool
>>> 22. In IE - added new message "Frog in pool with Chrome user included"
>>> in a pool in which the Chrome user is a member
>>>
>>
>
Re: Rel 1.2 RC2 tests
Posted by Ethan Jewett <es...@gmail.com>.
Sounds good. I've been using Stax a little bit every day and I haven't
noticed anything amiss aside from the small bug I filed in the
backlog.
Ethan
On Thursday, March 3, 2011, Richard Hirsch <hi...@gmail.com> wrote:
> I'm going to continue my tests today and then I'll cut a 1.2 release
> either tomorrow or Monday.
>
> D.
>
> On Tue, Mar 1, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> Hi,.
>>
>> I'm currently testing the stax deplyoment.
>>
>> I'll be testing each day a little bit.
>>
>> Instead of random tests, I'm trying to test the complete functionality
>> as good as possible.
>>
>> I'll be documenting my tests, so other community members know what has
>> been tested.
>>
>> Others should document their tests as well, so that we have a basic
>> release test plan that we can use for future releases:
>>
>> D.
>>
>> ---------------------
>> Browser Chrome
>>
>> 1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
>> in a incognito window
>> 2. Create new user via sign-up page
>> 3. Created message "Test #Retz @h" from main page
>> 4. Clicked @h link
>> 5. Page to main page via "Home" link
>> 6. Clicked on #Retz link
>> 7. Clicked on "test12rc2"
>> 8. Clicked on "Streams" page
>> 9. Created message "Streams message"
>> 10. Returned to main page via click on ESME icon
>> 11. Clicked on public link
>> 12. Clicked on "My Profile" link
>> 13. Changed first name, last name
>> 14. Clicked on "My Tracks"
>> 15. Added Track for "Frog"
>> 16. Opened ESME in another browser (IE) with another user
>> 17. Added message "Frog track test"
>> 18. Checked in Chrome whether message from IE user appears
>> 19. Set Frog track to "inactive"
>> 20. In IE - added new message "Frog track test-inactive"
>> 21. Check in Chrome whether message "Frog track test-inactive" appears
>> 22. Delete track "Frog"
>> 20. In IE - added new message "Frog track test-deleted"
>> 21. Check in Chrome whether message "Frog track test-deleted" appears
>> 22. Added Track for "Frog"
>> 20. In IE - added new message "Frog track in pool" in a pool in which
>> the Chrome user is not a member
>> 21. In IE added Chrome user to the pool
>> 22. In IE - added new message "Frog in pool with Chrome user included"
>> in a pool in which the Chrome user is a member
>>
>
Re: Rel 1.2 RC2 tests
Posted by Richard Hirsch <hi...@gmail.com>.
I'm going to continue my tests today and then I'll cut a 1.2 release
either tomorrow or Monday.
D.
On Tue, Mar 1, 2011 at 9:14 AM, Richard Hirsch <hi...@gmail.com> wrote:
> Hi,.
>
> I'm currently testing the stax deplyoment.
>
> I'll be testing each day a little bit.
>
> Instead of random tests, I'm trying to test the complete functionality
> as good as possible.
>
> I'll be documenting my tests, so other community members know what has
> been tested.
>
> Others should document their tests as well, so that we have a basic
> release test plan that we can use for future releases:
>
> D.
>
> ---------------------
> Browser Chrome
>
> 1. Opened ESME (http://esmecloudserverapache.dickhirsch.staxapps.net/)
> in a incognito window
> 2. Create new user via sign-up page
> 3. Created message "Test #Retz @h" from main page
> 4. Clicked @h link
> 5. Page to main page via "Home" link
> 6. Clicked on #Retz link
> 7. Clicked on "test12rc2"
> 8. Clicked on "Streams" page
> 9. Created message "Streams message"
> 10. Returned to main page via click on ESME icon
> 11. Clicked on public link
> 12. Clicked on "My Profile" link
> 13. Changed first name, last name
> 14. Clicked on "My Tracks"
> 15. Added Track for "Frog"
> 16. Opened ESME in another browser (IE) with another user
> 17. Added message "Frog track test"
> 18. Checked in Chrome whether message from IE user appears
> 19. Set Frog track to "inactive"
> 20. In IE - added new message "Frog track test-inactive"
> 21. Check in Chrome whether message "Frog track test-inactive" appears
> 22. Delete track "Frog"
> 20. In IE - added new message "Frog track test-deleted"
> 21. Check in Chrome whether message "Frog track test-deleted" appears
> 22. Added Track for "Frog"
> 20. In IE - added new message "Frog track in pool" in a pool in which
> the Chrome user is not a member
> 21. In IE added Chrome user to the pool
> 22. In IE - added new message "Frog in pool with Chrome user included"
> in a pool in which the Chrome user is a member
>