History

Paul Yang 188f18044f All integer types should accept null in json. (#3869 )		2017-11-13 09:31:28 -08:00
..
third_party/jsoncpp	Make conformance tests build for C++ and Java.	2015-12-16 13:38:10 -08:00
autoload.php	Fix php well known type conformance tests (#3828 ) (#3840 )	2017-11-04 09:33:56 -07:00
conformance_cpp.cc	Integrated internal changes from Google	2017-09-14 10:03:57 -07:00
conformance_nodejs.js	Merge from master	2017-07-25 11:52:33 -07:00
conformance_objc.m	Review feedback.	2017-07-26 16:24:05 -04:00
conformance_php.php	Fix php well known type conformance tests (#3828 ) (#3840 )	2017-11-04 09:33:56 -07:00
conformance_python.py	Merge from master	2017-07-25 11:52:33 -07:00
conformance_ruby.rb	Merge from master	2017-07-25 11:52:33 -07:00
conformance_test_runner.cc	Integrate internal changes	2016-10-10 11:23:36 -07:00
conformance_test.cc	All integer types should accept null in json. (#3869 )	2017-11-13 09:31:28 -08:00
conformance_test.h	Reserve unknown in Ruby (#3763 )	2017-10-26 14:41:43 -07:00
conformance.proto	Update the comment on the message_type to cover what it should be.	2017-07-26 17:07:01 -04:00
ConformanceJava.java	Merge from master	2017-07-25 11:52:33 -07:00
ConformanceJavaLite.java	Fix spelling in strings and comments	2016-07-03 15:26:04 +03:00
failure_list_cpp.txt	Update conformance tests	2017-07-25 12:22:32 -07:00
failure_list_csharp.txt	Reserve unknown in Ruby (#3763 )	2017-10-26 14:41:43 -07:00
failure_list_java.txt	Merge from master	2017-07-25 11:52:33 -07:00
failure_list_js.txt	Fix JS conformance tests	2017-10-18 15:09:21 -07:00
failure_list_objc.txt	Properly error on a tag with field number zero.	2017-06-06 10:14:41 -04:00
failure_list_php_c.txt	Add well-known timestamps to JSON for PHP (#3564 )	2017-09-10 15:17:50 -07:00
failure_list_php_zts_c.txt	Add json encode/decode for php. (#3226 )	2017-06-30 12:14:09 -07:00
failure_list_php.txt	Fix php well known type conformance tests (#3828 ) (#3840 )	2017-11-04 09:33:56 -07:00
failure_list_python_cpp.txt	Merge from google internal	2017-10-18 12:22:18 -07:00
failure_list_python-post26.txt	Updated C#'s failure list, and added missing file.	2016-01-11 16:15:46 -08:00
failure_list_python.txt	Merge from google internal	2017-10-18 12:22:18 -07:00
failure_list_ruby.txt	Reserve unknown in Ruby (#3763 )	2017-10-26 14:41:43 -07:00
Makefile.am	Fix php well known type conformance tests (#3828 ) (#3840 )	2017-11-04 09:33:56 -07:00
README.md	Removed obsolete comments and added docs.	2017-03-16 15:19:09 -07:00
update_failure_list.py	file() was removed in Python 3, use open() instead	2017-08-18 01:04:17 +02:00

README.md

Protocol Buffers - Google's data interchange format

This directory contains conformance tests for testing completeness and correctness of Protocol Buffers implementations. These tests are designed to be easy to run against any Protocol Buffers implementation.

This directory contains the tester process conformance-test, which contains all of the tests themselves. Then separate programs written in whatever language you want to test communicate with the tester program over a pipe.

Before running any of these tests, make sure you run make in the base directory to build protoc, since all the tests depend on it.

$ make

Running the tests for C++

To run the tests against the C++ implementation, run:

$ cd conformance && make test_cpp

Running the tests for JavaScript (Node.js)

To run the JavaScript tests against Node.js, make sure you have "node" on your path and then run:

$ cd conformance && make test_nodejs

Running the tests for Ruby (MRI)

To run the Ruby tests against MRI, first build the C extension:

$ cd ruby && rake

Then run the tests like so:

$ cd conformance && make test_ruby

Running the tests for other languages

Most of the languages in the Protobuf source tree are set up to run conformance tests. However some of them are more tricky to set up properly. See tests.sh in the base of the repository to see how Travis runs the tests.

Testing other Protocol Buffer implementations

To run these tests against a new Protocol Buffers implementation, write a program in your language that uses the protobuf implementation you want to test. This program should implement the testing protocol defined in conformance.proto. This is designed to be as easy as possible: the C++ version is only 150 lines and is a good example for what this program should look like (see conformance_cpp.cc). The program only needs to be able to read from stdin and write to stdout.

Portability

Note that the test runner currently does not work on Windows. Patches to fix this are welcome! (But please get in touch first to settle on a general implementation strategy).