[JBoss JIRA] (GTNMOP-54) Tests in WorkspaceTestCase are order dependent
by Peter Palaga (JIRA)
Peter Palaga created GTNMOP-54:
----------------------------------
Summary: Tests in WorkspaceTestCase are order dependent
Key: GTNMOP-54
URL: https://issues.jboss.org/browse/GTNMOP-54
Project: GateIn Model Object for Portal
Issue Type: Bug
Reporter: Peter Palaga
Assignee: Peter Palaga
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1091114
Description of problem:
Community MOP Core project (https://github.com/gatein/gatein-mop/tree/1.3.1.Final/core) has test dependency junit-4.10.jar (managed from gatein-dep-1.4.0.Final).
Prod MOP Core (http://git.app.eng.bos.redhat.com/git/gatein/gatein-mop.git/tree/core?id=...) has test dependency junit-4.11-redhat-1.jar.
There are junit 4.11 release notes: https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#t...
Test execution order has changed between junit 4.10 and 4.11. I get test failures in org.gatein.mop.core.api.workspace.WorkspaceTestCase. It depends on order of execution of org.gatein.mop.core.api.workspace.WorkspaceTestCase.testRemoveReferencedTemplate. When the test is runned, all following tests, where a site "portal" is added (.addSite(ObjectType.PORTAL_SITE, "portal")), fails. In junit 4.10 the test is runned in the end of the test file so the tests passed but in 4.11 5 tests fails with ERROR org.chromattic.core.DomainSession - Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.mop.core.api.workspace.PortalSite,typeName=mop:portalsite]] as an existing child with name mop:portal child of node /mop:workspace/mop:portalsites
Version-Release number of selected component (if applicable):
community MOP: 1.3.1.Final with junit 4.10
prod MOP: 1.3.1.Final-redhat-1 with junit 4.11-redhat-1
Additional info:
When I declare junit version to 4.11 in community project I get the errors.
When I declare junit version to 4.10-redhat-2 in prod project all tests passed.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNSSO-8) Unit tests
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNSSO-8?page=com.atlassian.jira.plugin.s... ]
Marek Posolda updated GTNSSO-8:
-------------------------------
Fix Version/s: 1.4.2.Final
(was: 1.4.1.Final)
> Unit tests
> ----------
>
> Key: GTNSSO-8
> URL: https://issues.jboss.org/browse/GTNSSO-8
> Project: GateIn SSO
> Issue Type: Enhancement
> Affects Versions: 1.1.1-GA
> Reporter: Marek Posolda
> Assignee: Marek Posolda
> Fix For: 1.4.2.Final
>
>
> Current support of unit tests is not good. There are couple of dummy unit tests, but they are disabled as they require server to be running before running tests. It will be needed to provide integration with some well-known solution (Arquillian, Cargo, JBoss unit...) and provide more unit tests for SSO component.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ]
Marek Posolda updated GTNSSO-28:
--------------------------------
Fix Version/s: 1.4.2.Final
> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
> Key: GTNSSO-28
> URL: https://issues.jboss.org/browse/GTNSSO-28
> Project: GateIn SSO
> Issue Type: Bug
> Affects Versions: 1.4.0.Beta01
> Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
> Reporter: Michael McKinsey
> Assignee: Marek Posolda
> Fix For: 1.4.2.Final
>
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://./openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F.%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1...
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing an error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months