The odd thing is though that my local partuza install has 42 failures,
while partuza.nl (1.5 week old) has X.
The code for partuza, php shindig, database.. even the information in
the db is identical between the 2 versions, only the shindig/features
code is different between the two.
It might well be that the JS code is correct and exposed some flaws in
the existing logic, but it still looks a bit funny though
-- Chris
On Aug 22, 2008, at 11:04 PM, Cassie wrote:
I check the compliance tests regularly for the actual deployment of
Shindig
that I work on at work. We are failing more now only because the
tests are
getting much more thorough. (The tests are also very active so
sometimes
they have bugs too although it is usually our code that's wrong :)
I haven't found many issues with Shindig's actual js layer though -
its
usually been in the server layer and most often in the service
implementations that are container specific.
The non-rpc based container definitely has some issues though
because it
sending requests to the server in a json map format... which doesn't
preserve order. So, some of the compliance tests would fail simply
because
they were fetching app data before it was updated and so forth.
So... hopefully someone out there can get a patch to switch the php
to rpc
batching going :)
- Cassie
On Fri, Aug 22, 2008 at 12:28 PM, Dan Peterson
<[EMAIL PROTECTED]> wrote:
By the way, the docs for the compliance test suite are at:
http://code.google.com/p/opensocial-resources/wiki/ComplianceTests
-Dan
On Fri, Aug 22, 2008 at 12:22 PM, Louis Ryan <[EMAIL PROTECTED]>
wrote:
Im seeing some similar issues. One thing I noticed is that
lookingFor is
now
an Enum in JS but its not the Java datamodel. Im going to fix that
one.
On Fri, Aug 22, 2008 at 11:54 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
When running the compliance test suite:
http://opensocial-resources.googlecode.com/svn/tests/trunk/suites/0.7/compliance/reference/reference.xml
I get 28 failed on my live version of partuza+php shindig (
www.partuza.nl is
running a checkout that is about 1.5 weeks old), while the latest
code
locally gives me 42 errors.
To rule out that it wasn't the php code, i updated just shindig/
php on
the
live server, and the error count didn't change, so it's probably
some
shindig//features/* changes that cause this.
Anyone checking if our JS code is 'compliant' ? And/or working on
fixing
it? Seems right now it's only getting less so :)
-- Chris
