[jira] Closed: (BEEHIVE-356) Patch for a new coreWeb MockPortal BVT

["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