aboutsummaryrefslogtreecommitdiffhomepage
path: root/conformance/failure_list_cpp.txt
Commit message (Collapse)AuthorAge
* Enable ignoring unknown in json parsing in php (#4839)Gravatar Paul Yang2018-07-09
| | | | | | | | | | * Enable ignoring unknown in json parsing in php * Update generated descriptor files * Update failure list for other languages. * Remove unnecessary php files
* Integrated internal changes from GoogleGravatar Adam Cozzette2017-12-01
|
* Update conformance testsGravatar Jisi Liu2017-07-25
|
* Merge from masterGravatar Jisi Liu2017-07-25
|
* Merge from Google internal for 3.4 releaseGravatar Jisi Liu2017-07-18
|
* Down-integrate from google3.Gravatar Feng Xiao2017-03-29
|
* Integrated internal changes from GoogleGravatar Adam Cozzette2016-11-17
|
* Fix bugs for internal integration.Gravatar Bo Yang2016-10-10
|
* Integrate internal changesGravatar Bo Yang2016-10-10
|
* Add note about JSON tests maybe being wrong. (#1992)Gravatar Thomas Van Lenten2016-08-23
| | | | | | | | Add note about JSON tests maybe being wrong. - Add note about the JSON test maybe not being correct yet. - Add test to checks the generated names for double underscores to be sure they are what is expected.
* More JSON testsGravatar Thomas Van Lenten2016-08-22
| | | | | - String behaviors - Testing only valid JSON is allowed
* Make conformance tests more strict about the failure list.Gravatar Josh Haberman2016-06-03
| | | | | | The failure lists were falling out of date because the tests would pass even if people forgot to remove failures from the list.
* Allow conformance test runner to tolerate crashes, and re-enable conformance ↵Gravatar Josh Haberman2016-01-11
| | | | tests.
* Down-integrate from internal code base.Gravatar Feng Xiao2015-12-11
|
* Added support for Json and valid input to conformance tests.Gravatar Josh Haberman2015-07-10
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Removed test_name from conformance.proto.Gravatar Josh Haberman2015-06-04
| | | | Change-Id: I382dcda97fa123a6da4ff5faad5d7ece95853f33
* Conformance tests can now be excluded based on their names.Gravatar Josh Haberman2015-06-03
This allows us to enable conformance tests even when we know that some tests are failing and need to be fixed. Change-Id: I372f43663008747db6f2b2cf06e6ffa4c6d85b2d