You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Nathan Jantz (JIRA)" <be...@incubator.apache.org> on 2005/02/24 19:27:49 UTC
[jira] Created: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Patch for a new coreWeb MockPortal BVT
--------------------------------------
Key: BEEHIVE-356
URL: http://issues.apache.org/jira/browse/BEEHIVE-356
Project: Beehive
Type: Test
Components: NetUI
Versions: V1Beta
Environment: Windows running the usual required components for Beehive.
Reporter: Nathan Jantz
Assigned to: Rich Feit
Fix For: V1Beta
Attachments: patch.txt
Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
Here is the svn add log on what files were added and where:
D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
A scoping2
A scoping2\index.jsp
A scoping2\results.jsp
A scoping2\ScopedPortal.jsp
A scoping2\ScopingController.jpf
A scoping2\window1.jsp
A scoping2\window1Results.jsp
D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
A MockPortalScopingTest2.xml
I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-356?page=history ]
Rich Feit resolved BEEHIVE-356:
-------------------------------
Resolution: Won't Fix
Hi Nathan,
I just put this in locally and realized something. I'm really sorry about this, but my checkin for revision 155201 totally invalidates all of your test results. I went back and re-recorded all the tests that had anything to do with popup windows.
I think the new MockPortalPopupWindows test covers the spirit of this test -- if it doesn't, would you reopen this bug on me?
Again, sorry for the mixup.
> Patch for a new coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-356
> URL: http://issues.apache.org/jira/browse/BEEHIVE-356
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Rich Feit
> Fix For: V1Beta
> Attachments: patch.txt
>
> Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
> This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
> Here is the svn add log on what files were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
> A scoping2
> A scoping2\index.jsp
> A scoping2\results.jsp
> A scoping2\ScopedPortal.jsp
> A scoping2\ScopingController.jpf
> A scoping2\window1.jsp
> A scoping2\window1Results.jsp
> D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
> A MockPortalScopingTest2.xml
> I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-356?page=history ]
Nathan Jantz updated BEEHIVE-356:
---------------------------------
Attachment: patch.txt
Attaching the patch file.
> Patch for a new coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-356
> URL: http://issues.apache.org/jira/browse/BEEHIVE-356
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Rich Feit
> Fix For: V1Beta
> Attachments: patch.txt
>
> Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
> This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
> Here is the svn add log on what files were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
> A scoping2
> A scoping2\index.jsp
> A scoping2\results.jsp
> A scoping2\ScopedPortal.jsp
> A scoping2\ScopingController.jpf
> A scoping2\window1.jsp
> A scoping2\window1Results.jsp
> D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
> A MockPortalScopingTest2.xml
> I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-356?page=history ]
Rich Feit resolved BEEHIVE-356:
-------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
Resolution: Fixed
OK, this is in with revision 155637. Thanks for the test.
> Patch for a new coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-356
> URL: http://issues.apache.org/jira/browse/BEEHIVE-356
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Nathan Jantz
> Fix For: V1Beta
> Attachments: patch.txt
>
> Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
> This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
> Here is the svn add log on what files were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
> A scoping2
> A scoping2\index.jsp
> A scoping2\results.jsp
> A scoping2\ScopedPortal.jsp
> A scoping2\ScopingController.jpf
> A scoping2\window1.jsp
> A scoping2\window1Results.jsp
> D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
> A MockPortalScopingTest2.xml
> I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-356?page=history ]
Rich Feit reassigned BEEHIVE-356:
---------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
> Patch for a new coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-356
> URL: http://issues.apache.org/jira/browse/BEEHIVE-356
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Nathan Jantz
> Fix For: V1Beta
> Attachments: patch.txt
>
> Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
> This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
> Here is the svn add log on what files were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
> A scoping2
> A scoping2\index.jsp
> A scoping2\results.jsp
> A scoping2\ScopedPortal.jsp
> A scoping2\ScopingController.jpf
> A scoping2\window1.jsp
> A scoping2\window1Results.jsp
> D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
> A MockPortalScopingTest2.xml
> I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-356?page=history ]
Nathan Jantz closed BEEHIVE-356:
--------------------------------
I'm closing this because checkin for revision 155201 the invalidates the test results. MockPortalPopupWindows tests now cover the spirit of the original tests.
> Patch for a new coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-356
> URL: http://issues.apache.org/jira/browse/BEEHIVE-356
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Nathan Jantz
> Fix For: V1Beta
> Attachments: patch.txt
>
> Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
> This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
> Here is the svn add log on what files were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
> A scoping2
> A scoping2\index.jsp
> A scoping2\results.jsp
> A scoping2\ScopedPortal.jsp
> A scoping2\ScopingController.jpf
> A scoping2\window1.jsp
> A scoping2\window1Results.jsp
> D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
> A MockPortalScopingTest2.xml
> I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Reopened: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-356?page=history ]
Rich Feit reopened BEEHIVE-356:
-------------------------------
Assign To: Rich Feit (was: Nathan Jantz)
OK, I've got this test up and running -- there's value in it, and I'm just going to re-record it based on the URIs that I see in the original test file from the patch.
> Patch for a new coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-356
> URL: http://issues.apache.org/jira/browse/BEEHIVE-356
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Rich Feit
> Fix For: V1Beta
> Attachments: patch.txt
>
> Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
> This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
> Here is the svn add log on what files were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
> A scoping2
> A scoping2\index.jsp
> A scoping2\results.jsp
> A scoping2\ScopedPortal.jsp
> A scoping2\ScopingController.jpf
> A scoping2\window1.jsp
> A scoping2\window1Results.jsp
> D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
> A MockPortalScopingTest2.xml
> I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-356?page=history ]
Nathan Jantz closed BEEHIVE-356:
--------------------------------
Test implemented. Closing now.
> Patch for a new coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-356
> URL: http://issues.apache.org/jira/browse/BEEHIVE-356
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components for Beehive.
> Reporter: Nathan Jantz
> Assignee: Nathan Jantz
> Fix For: V1Beta
> Attachments: patch.txt
>
> Submitting a new patch to add a new BVT to the existing coreWeb MockPortal tests. Test name for this is MockPortalScopingTest2
> This BVT is similar to the last BVT added for MockPortal but with a slight difference in how the pop-up is spawned. Basically, a pop-up window is spawned from a portlet (but this time via a netui:anchor tag not javascript) from a form post to a specific targetScope and verifying the pop-up window has access to data defined in that scope. Then the pop-up window posts new data to that scope and verifies that the portlet now sees the new data in the same defined scope.
> Here is the svn add log on what files were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping2
> A scoping2
> A scoping2\index.jsp
> A scoping2\results.jsp
> A scoping2\ScopedPortal.jsp
> A scoping2\ScopingController.jpf
> A scoping2\window1.jsp
> A scoping2\window1Results.jsp
> D:\beehive\trunk\netui\test\webapps\drt\testRecorder\tests>svn add MockPortalScopingTest2.xml
> A MockPortalScopingTest2.xml
> I will attach the patch file here shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira