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/09 21:33:12 UTC
[jira] Created: (BEEHIVE-267) Patch for new a coreWeb MockPortal BVT
Patch for new a coreWeb MockPortal BVT
--------------------------------------
Key: BEEHIVE-267
URL: http://issues.apache.org/jira/browse/BEEHIVE-267
Project: Beehive
Type: Test
Components: NetUI
Versions: V1Beta
Environment: Windows running the usual required components of Beehive.
Reporter: Nathan Jantz
Priority: Minor
Attachments: patch.txt
Submitting a patch to add a new BVT to the existing coreWeb MockPortal tests. This BVT verifies functionality of the jpfScopingID parameter and targetScope attribute using portlets.
Basically, a pop-up window is spawned from a portlet 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 svn add log on what fiels were added and where:
D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping
A scoping
A scoping\index.jsp
A scoping\results.jsp
A scoping\ScopedPortal.jsp
A scoping\ScopingController.jpf
A scoping\window1.jsp
A scoping\window1Results.jsp
I will attach the patch file here shortly.
-nathan
--
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-267) Patch for new a coreWeb MockPortal BVT
Posted by "Alejandro Ramirez (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-267?page=history ]
Alejandro Ramirez reassigned BEEHIVE-267:
-----------------------------------------
Assign To: Rich Feit
> Patch for new a coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-267
> URL: http://issues.apache.org/jira/browse/BEEHIVE-267
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components of Beehive.
> Reporter: Nathan Jantz
> Assignee: Rich Feit
> Priority: Minor
> Attachments: patch.txt
>
> Submitting a patch to add a new BVT to the existing coreWeb MockPortal tests. This BVT verifies functionality of the jpfScopingID parameter and targetScope attribute using portlets.
> Basically, a pop-up window is spawned from a portlet 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 svn add log on what fiels were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping
> A scoping
> A scoping\index.jsp
> A scoping\results.jsp
> A scoping\ScopedPortal.jsp
> A scoping\ScopingController.jpf
> A scoping\window1.jsp
> A scoping\window1Results.jsp
> I will attach the patch file here shortly.
> -nathan
--
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-267) Patch for new a coreWeb MockPortal BVT
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-267?page=history ]
Nathan Jantz updated BEEHIVE-267:
---------------------------------
Attachment: patch.txt
Adding patch file.
> Patch for new a coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-267
> URL: http://issues.apache.org/jira/browse/BEEHIVE-267
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components of Beehive.
> Reporter: Nathan Jantz
> Priority: Minor
> Attachments: patch.txt
>
> Submitting a patch to add a new BVT to the existing coreWeb MockPortal tests. This BVT verifies functionality of the jpfScopingID parameter and targetScope attribute using portlets.
> Basically, a pop-up window is spawned from a portlet 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 svn add log on what fiels were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping
> A scoping
> A scoping\index.jsp
> A scoping\results.jsp
> A scoping\ScopedPortal.jsp
> A scoping\ScopingController.jpf
> A scoping\window1.jsp
> A scoping\window1Results.jsp
> I will attach the patch file here shortly.
> -nathan
--
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-267) Patch for new a coreWeb MockPortal BVT
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-267?page=history ]
Nathan Jantz closed BEEHIVE-267:
--------------------------------
I'm closing this because checkin for revision 155201 invalidates the test results. MockPortalPopupWindows tests now cover the spirit of the original tests.
> Patch for new a coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-267
> URL: http://issues.apache.org/jira/browse/BEEHIVE-267
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components of Beehive.
> Reporter: Nathan Jantz
> Assignee: Nathan Jantz
> Priority: Minor
> Fix For: V1Beta
> Attachments: patch.txt, patch2.txt
>
> Submitting a patch to add a new BVT to the existing coreWeb MockPortal tests. This BVT verifies functionality of the jpfScopingID parameter and targetScope attribute using portlets.
> Basically, a pop-up window is spawned from a portlet 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 svn add log on what fiels were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping
> A scoping
> A scoping\index.jsp
> A scoping\results.jsp
> A scoping\ScopedPortal.jsp
> A scoping\ScopingController.jpf
> A scoping\window1.jsp
> A scoping\window1Results.jsp
> I will attach the patch file here shortly.
> -nathan
--
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-267) Patch for new a coreWeb MockPortal BVT
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-267?page=history ]
Rich Feit resolved BEEHIVE-267:
-------------------------------
Resolution: Fixed
Fix Version: V1Beta
Added with revision 154639. Thanks for the contribution, and sorry for the delay.
> Patch for new a coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-267
> URL: http://issues.apache.org/jira/browse/BEEHIVE-267
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components of Beehive.
> Reporter: Nathan Jantz
> Assignee: Rich Feit
> Priority: Minor
> Fix For: V1Beta
> Attachments: patch.txt, patch2.txt
>
> Submitting a patch to add a new BVT to the existing coreWeb MockPortal tests. This BVT verifies functionality of the jpfScopingID parameter and targetScope attribute using portlets.
> Basically, a pop-up window is spawned from a portlet 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 svn add log on what fiels were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping
> A scoping
> A scoping\index.jsp
> A scoping\results.jsp
> A scoping\ScopedPortal.jsp
> A scoping\ScopingController.jpf
> A scoping\window1.jsp
> A scoping\window1Results.jsp
> I will attach the patch file here shortly.
> -nathan
--
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-267) Patch for new a coreWeb MockPortal BVT
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-267?page=history ]
Rich Feit reassigned BEEHIVE-267:
---------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
> Patch for new a coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-267
> URL: http://issues.apache.org/jira/browse/BEEHIVE-267
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components of Beehive.
> Reporter: Nathan Jantz
> Assignee: Nathan Jantz
> Priority: Minor
> Fix For: V1Beta
> Attachments: patch.txt, patch2.txt
>
> Submitting a patch to add a new BVT to the existing coreWeb MockPortal tests. This BVT verifies functionality of the jpfScopingID parameter and targetScope attribute using portlets.
> Basically, a pop-up window is spawned from a portlet 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 svn add log on what fiels were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping
> A scoping
> A scoping\index.jsp
> A scoping\results.jsp
> A scoping\ScopedPortal.jsp
> A scoping\ScopingController.jpf
> A scoping\window1.jsp
> A scoping\window1Results.jsp
> I will attach the patch file here shortly.
> -nathan
--
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-267) Patch for new a coreWeb MockPortal BVT
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-267?page=history ]
Nathan Jantz updated BEEHIVE-267:
---------------------------------
Attachment: patch2.txt
I forgot to include the test recorder xml comparison file in the first patch, so here it is by itself in a second patch file.
> Patch for new a coreWeb MockPortal BVT
> --------------------------------------
>
> Key: BEEHIVE-267
> URL: http://issues.apache.org/jira/browse/BEEHIVE-267
> Project: Beehive
> Type: Test
> Components: NetUI
> Versions: V1Beta
> Environment: Windows running the usual required components of Beehive.
> Reporter: Nathan Jantz
> Assignee: Rich Feit
> Priority: Minor
> Attachments: patch.txt, patch2.txt
>
> Submitting a patch to add a new BVT to the existing coreWeb MockPortal tests. This BVT verifies functionality of the jpfScopingID parameter and targetScope attribute using portlets.
> Basically, a pop-up window is spawned from a portlet 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 svn add log on what fiels were added and where:
> D:\beehive\trunk\netui\test\webapps\drt\coreWeb\mockportal>svn add scoping
> A scoping
> A scoping\index.jsp
> A scoping\results.jsp
> A scoping\ScopedPortal.jsp
> A scoping\ScopingController.jpf
> A scoping\window1.jsp
> A scoping\window1Results.jsp
> I will attach the patch file here shortly.
> -nathan
--
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