tree: 0d10b52db82e95b0ea6b5f7a77cff4f552eb9c0a [path history] [tgz]
  1. ConformanceJava.java
  2. ConformanceJavaLite.java
  3. Makefile.am
  4. README.md
  5. conformance.proto
  6. conformance_cpp.cc
  7. conformance_objc.m
  8. conformance_python.py
  9. conformance_ruby.rb
  10. conformance_test.cc
  11. conformance_test.h
  12. conformance_test_runner.cc
  13. failure_list_cpp.txt
  14. failure_list_csharp.txt
  15. failure_list_java.txt
  16. failure_list_objc.txt
  17. failure_list_python-post26.txt
  18. failure_list_python.txt
  19. failure_list_python_cpp.txt
  20. failure_list_ruby.txt
  21. third_party/
conformance/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).