Hide Forgot
An inspiration can be taken from https://github.com/arquillian/arquillian-extension-portal/blob/master/portal/impl/ftest/src/test/integration/org/jboss/arquillian/portal/impl/it/JSFPortletTest.java and https://github.com/arquillian/arquillian-extension-portal/blob/master/warp/jsf-portlet/src/test/integration/org/jboss/arquillian/portal/warp/jsf/it/JSFPortletWarpTest.java Low priority, can be postponed to JBoss Portal 6.2
Status update: The setup Ken is using in arquillian-extension-portal works with a bare bone AS plus gatein-pc. This is not enough in quickstarts as we want to have access to Portal public APIs (navigation, organization, ...) too, which we (and customers) use in portlets. This is solvable trough taking full-blown Portal instead of AS+PC, but in this way, there is no app in the container that would render a (per-request) given single portlet on a page. This could be solved by the planned public API enhancements which are worked on within Bug 1043858. Bug 1043858 is targeted for JBoss Portal 6.2, thus I am postponing this one too. There was an objection that taking a full-blown Portal is an overkill, because it takes too long to boot. This can perhaps be solved by using a remote container rather than a managed one. If this solution is not sufficient for some reason, we'd probably need to find out a way how to make the portal booting faster through stripping away some parts that are not necessary for this kind of portlet testing. Other proposals are welcome. My efforts can be seen in this branch: https://github.com/ppalaga/jboss-portal-quickstarts/tree/BZ1036823
Deferred as it cannot be done elegantly with the present Page Composition API (as I originally hoped). Page Composition API would have to be accessible through REST so that it can be used for creating ad hoc pages for the sake of UI testing.