Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Jisi Liu 1a7a7fca80 Merge from google internal 7 years ago
..
third_party/jsoncpp Make conformance tests build for C++ and Java. 9 years ago
ConformanceJava.java Merge from master 7 years ago
ConformanceJavaLite.java Fix spelling in strings and comments 9 years ago
Makefile.am Generate the proto2 test file and link it in for ObjC. 7 years ago
README.md Removed obsolete comments and added docs. 8 years ago
autoload.php Add json encode/decode for php. (#3226) 8 years ago
conformance.proto Update the comment on the message_type to cover what it should be. 7 years ago
conformance_cpp.cc Integrated internal changes from Google 7 years ago
conformance_nodejs.js Merge from master 7 years ago
conformance_objc.m Review feedback. 7 years ago
conformance_php.php Add well-known timestamps to JSON for PHP (#3564) 7 years ago
conformance_python.py Merge from master 7 years ago
conformance_ruby.rb Merge from master 7 years ago
conformance_test.cc Merge pull request #2377 from mcos/chore/conformance-null-tests 7 years ago
conformance_test.h Merge from master 7 years ago
conformance_test_runner.cc Integrate internal changes 8 years ago
failure_list_cpp.txt Update conformance tests 7 years ago
failure_list_csharp.txt Merge remote-tracking branch 'origin/3.4.x' into mergemaster 7 years ago
failure_list_java.txt Merge from master 7 years ago
failure_list_js.txt Merge from master 7 years ago
failure_list_objc.txt Properly error on a tag with field number zero. 8 years ago
failure_list_php.txt Add well-known timestamps to JSON for PHP (#3564) 7 years ago
failure_list_php_c.txt Add well-known timestamps to JSON for PHP (#3564) 7 years ago
failure_list_php_zts_c.txt Add json encode/decode for php. (#3226) 8 years ago
failure_list_python-post26.txt Updated C#'s failure list, and added missing file. 9 years ago
failure_list_python.txt Merge from google internal 7 years ago
failure_list_python_cpp.txt Merge from google internal 7 years ago
failure_list_ruby.txt Update conformance tests again. 7 years ago
update_failure_list.py file() was removed in Python 3, use open() instead 7 years ago

README.md

Protocol Buffers - Google's data interchange format

Build Status

Copyright 2008 Google Inc.

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).