- 27 Jul, 2018 1 commit
-
-
Paul Yang authored
* Give a unique category to each test. This change introduce a TestCategory enum to ConformanceRequest. Existing tests are divided into three categories: binary format test, json format test and json format (ignore unknown when parsing) test. For the previous two categories, there is no change to existing testee programs. For tests with the last category, testee programs should either enable ignoring unknown field during json parsing or skip the test. * Fix python test * Fix java * Fix csharp * Update document * Update csharp generated code
-
- 14 Mar, 2018 1 commit
-
-
Adam Cozzette authored
We no longer need this, now that we have finished the switch to C++11 and are using std::unique_ptr.
-
- 14 Sep, 2017 1 commit
-
-
Adam Cozzette authored
-
- 25 Jul, 2017 1 commit
-
-
Jisi Liu authored
-
- 01 Jul, 2017 1 commit
-
-
Yilun Chong authored
-
- 29 Jun, 2017 1 commit
-
-
Yilun Chong authored
-
- 28 Jun, 2017 1 commit
-
-
Yilun Chong authored
-
- 09 Dec, 2016 1 commit
-
-
Julien Brianceau authored
-
- 03 Dec, 2016 1 commit
-
-
Joshua Haberman authored
* Factored Conformance test messages into shared test schema. * Updated benchmarks to use new proto3 message locations. * Fixed include path. * Conformance: fixed include of Python test messages. * Make maven in Rakefile use --batch-mode. * Revert changes to benchmarks. On second thought I think a separate schema for CPU benchmarking makes sense. * Try regenerating C# protos for new test protos. * Removed benchmark messages from test proto. * Added Jon Skeet's fixes for C#. * Removed duplicate/old test messages C# file. * C# fixes for test schema move. * Fixed C# to use the correct TestAllTypes message. * Fixes for Objective C test schema move. * Added missing EXTRA_DIST file.
-
- 12 Dec, 2015 1 commit
-
-
Feng Xiao authored
-
- 10 Jul, 2015 1 commit
-
-
Josh Haberman authored
This was enabled by the recent open-sourcing of JSON support and MessageDifferencer. MessageDifferencer allows the conformance suite to expand because it allows us to write tests for payloads that parse successfully. To verify the testee's output payload, we need to parse it back into a message and compare the message instances. Comparing output bytes vs. a golden message is *not* valid, because protobufs do not have a canonical encoding (especially in the presence of maps, which have no prescribed serialization order). We only add one small JSON test for now, but with the framework in place we now have the foundation to dramatically expand the coverage of the conformance test suite. Also added the ability for the testee to skip tests that exercise features that are unimplemented. This allows Java (which currently has no JSON support) to skip tests involving JSON. Change-Id: I697b4363da432b61ae3b638b4287c4cda1af4deb
-
- 08 Apr, 2015 1 commit
-
-
Josh Haberman authored
Change-Id: Ib75664194491643f8e4f1503a2ed942a2d1e1655
-