Chiebot-Mirror
/
protobuf
mirror of https://github.com/protocolbuffers/protobuf.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
4328 Commits
201 Branches
346 Tags
254 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 5af0b547de
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5af0b547de'
${ noResults }
protobuf/conformance
Joshua Haberman ffa71f8007
A few more cases for binary conformance tests. (#2500) 		8 years ago
..
third_party/jsoncpp Make conformance tests build for C++ and Java. 9 years ago
ConformanceJava.java Factored Conformance and Benchmark test messages into shared test schema. (#1971) 8 years ago
ConformanceJavaLite.java Fix spelling in strings and comments 9 years ago
Makefile.am Factored Conformance and Benchmark test messages into shared test schema. (#1971) 8 years ago
README.md Added first version of conformance tests. 10 years ago
conformance.proto Factored Conformance and Benchmark test messages into shared test schema. (#1971) 8 years ago
conformance_cpp.cc Fix #include in cc files 8 years ago
conformance_objc.m Factored Conformance and Benchmark test messages into shared test schema. (#1971) 8 years ago
conformance_python.py Factored Conformance and Benchmark test messages into shared test schema. (#1971) 8 years ago
conformance_ruby.rb Factored Conformance and Benchmark test messages into shared test schema. (#1971) 8 years ago
conformance_test.cc A few more cases for binary conformance tests. (#2500) 8 years ago
conformance_test.h Added conformance testing for binary primitive types. (#2491) 8 years ago
conformance_test_runner.cc Integrate internal changes 8 years ago
failure_list_cpp.txt Integrated internal changes from Google 8 years ago
failure_list_csharp.txt Update conformance failure lists. 8 years ago
failure_list_java.txt Updated failure_list_java.txt for Java conformance test 8 years ago
failure_list_objc.txt Record zero for "has" for proto3 if in a oneof. 8 years ago
failure_list_python-post26.txt Updated C#'s failure list, and added missing file. 9 years ago
failure_list_python.txt Integrated internal changes from Google 8 years ago
failure_list_python_cpp.txt Integrated internal changes from Google 8 years ago
failure_list_ruby.txt Update conformance failure lists. 8 years ago
update_failure_list.py Added update_failure_list.py. 9 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

Then to run the tests against the C++ implementation, run:

$ cd conformance && make test_cpp

More tests and languages will be added soon!

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