package protobuf_unittest

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

service AggregateService

unittest_custom_options.proto:362

service TestConflictingMethodNames

cpp_test_bad_identifiers.proto:121

service TestService

unittest.proto:712

service TestServiceWithCustomOptions

unittest_custom_options.proto:125

message Aggregate

unittest_custom_options.proto:306

A helper type used to test aggregate option parsing

enum AggregateEnum

unittest_custom_options.proto:369

message AggregateMessageSet

unittest_custom_options.proto:293

Used in: Aggregate

(message has no fields)

message AggregateMessageSetElement

unittest_custom_options.proto:298

message ComplexOpt6

unittest_custom_options.proto:264

message ComplexOptionType1

unittest_custom_options.proto:217

Used in: ComplexOptionType2

message ComplexOptionType2

unittest_custom_options.proto:225

message ComplexOptionType2.ComplexOptionType4

unittest_custom_options.proto:229

Used in: ComplexOptionType2

message ComplexOptionType3

unittest_custom_options.proto:242

message ComplexOptionType3.ComplexOptionType5

unittest_custom_options.proto:245

Used in: ComplexOptionType3

message CustomOptionFooClientMessage

unittest_custom_options.proto:119

(message has no fields)

message CustomOptionFooServerMessage

unittest_custom_options.proto:122

(message has no fields)

message CustomOptionMaxIntegerValues

unittest_custom_options.proto:181

(message has no fields)

message CustomOptionMinIntegerValues

unittest_custom_options.proto:167

(message has no fields)

message CustomOptionOtherValues

unittest_custom_options.proto:195

(message has no fields)

message DummyMessageContainingEnum

unittest_custom_options.proto:137

(message has no fields)

enum DummyMessageContainingEnum.TestEnumType

unittest_custom_options.proto:138

message DummyMessageInvalidAsOptionType

unittest_custom_options.proto:144

(message has no fields)

message FooClientMessage

unittest.proto:709

(message has no fields)

message FooServerMessage

unittest.proto:710

(message has no fields)

enum ForeignEnum

unittest.proto:182

Used in: TestAllTypes, TestCamelCaseFieldNames, TestDynamicExtensions, TestPackedTypes, TestUnpackedTypes

enum ForeignEnumLite

unittest_lite.proto:160

Used in: TestAllTypesLite, TestPackedTypesLite

message ForeignMessage

unittest.proto:178

Define these after TestAllTypes to make sure the compiler can handle that.

Used in: TestAllTypes, TestCamelCaseFieldNames, TestDynamicExtensions, TestNestedMessageHasBits.NestedMessage, TestOptimizedForSize

message ForeignMessageLite

unittest_lite.proto:156

Used in: TestAllTypesLite

enum MethodOpt1

unittest_custom_options.proto:83

message MoreBytes

unittest.proto:557

message MoreString

unittest.proto:549

message NestedOptionType

unittest_custom_options.proto:375

Test custom options for nested type.

(message has no fields)

enum NestedOptionType.NestedEnum

unittest_custom_options.proto:380

message NestedOptionType.NestedMessage

unittest_custom_options.proto:376

message OneBytes

unittest.proto:553

message OneString

unittest.proto:545

Test String and Bytes: string is for valid UTF-8 strings

message OptionalGroup_extension

unittest.proto:210

message OptionalGroup_extension_lite

unittest_lite.proto:205

message RawMessageSet

unittest_mset.proto:66

MessageSet wire format is equivalent to this.

message RawMessageSet.Item

unittest_mset.proto:67

Used in: RawMessageSet

message RepeatedGroup_extension

unittest.proto:250

message RepeatedGroup_extension_lite

unittest_lite.proto:247

message SettingRealsFromNegativeInts

unittest_custom_options.proto:209

(message has no fields)

message SettingRealsFromPositiveInts

unittest_custom_options.proto:204

(message has no fields)

message SparseEnumMessage

unittest.proto:540

message TestAllExtensions

unittest.proto:188

(message has no fields)

message TestAllExtensionsLite

unittest_lite.proto:183

(message has no fields)

message TestAllTypes

unittest.proto:60

This proto includes every type of field in both singular and repeated forms.

Used in: TestEagerMessage, TestLazyMessage, TestLiteImportsNonlite, TestParsingMerge, TestParsingMerge.OptionalGroup, TestParsingMerge.RepeatedFieldsGenerator, TestParsingMerge.RepeatedFieldsGenerator.Group1, TestParsingMerge.RepeatedFieldsGenerator.Group2, TestParsingMerge.RepeatedGroup

enum TestAllTypes.NestedEnum

unittest.proto:68

Used in: TestAllTypes

message TestAllTypes.NestedMessage

unittest.proto:61

Used in: TestAllTypes, TestForeignNested

message TestAllTypes.OptionalGroup

unittest.proto:91

Used in: TestAllTypes

message TestAllTypes.RepeatedGroup

unittest.proto:129

Used in: TestAllTypes

message TestAllTypesLite

unittest_lite.proto:44

Same as TestAllTypes but with the lite runtime.

Used in: TestParsingMergeLite, TestParsingMergeLite.OptionalGroup, TestParsingMergeLite.RepeatedFieldsGenerator, TestParsingMergeLite.RepeatedFieldsGenerator.Group1, TestParsingMergeLite.RepeatedFieldsGenerator.Group2, TestParsingMergeLite.RepeatedGroup

enum TestAllTypesLite.NestedEnum

unittest_lite.proto:49

Used in: TestAllTypesLite

message TestAllTypesLite.NestedMessage

unittest_lite.proto:45

Used in: TestAllTypesLite

message TestAllTypesLite.OptionalGroup

unittest_lite.proto:72

Used in: TestAllTypesLite

message TestAllTypesLite.RepeatedGroup

unittest_lite.proto:111

Used in: TestAllTypesLite

message TestCamelCaseFieldNames

unittest.proto:458

Test message with CamelCase field names. This violates Protocol Buffer standard style.

message TestCommentInjectionMessage

unittest.proto:699

message TestConflictingSymbolNames

cpp_test_bad_identifiers.proto:49

Test that fields can have names like "input" and "i" which are also used internally by the code generator for local variables.

message TestConflictingSymbolNames.BuildDescriptors

cpp_test_bad_identifiers.proto:50

(message has no fields)

message TestConflictingSymbolNames.Cord

cpp_test_bad_identifiers.proto:92

(message has no fields)

message TestConflictingSymbolNames.DO

cpp_test_bad_identifiers.proto:103

The generator used to #define a macro called "DO" inside the .cc file.

Used in: TestConflictingSymbolNames

(message has no fields)

message TestConflictingSymbolNames.Data1

cpp_test_bad_identifiers.proto:62

message TestConflictingSymbolNames.Data2

cpp_test_bad_identifiers.proto:63

message TestConflictingSymbolNames.Data3

cpp_test_bad_identifiers.proto:64

message TestConflictingSymbolNames.Data4

cpp_test_bad_identifiers.proto:65

message TestConflictingSymbolNames.Data5

cpp_test_bad_identifiers.proto:66

message TestConflictingSymbolNames.Data6

cpp_test_bad_identifiers.proto:67

message TestConflictingSymbolNames.StringPiece

cpp_test_bad_identifiers.proto:95

(message has no fields)

enum TestConflictingSymbolNames.TestEnum

cpp_test_bad_identifiers.proto:61

Used in: Data2

message TestConflictingSymbolNames.TypeTraits

cpp_test_bad_identifiers.proto:51

(message has no fields)

message TestConflictingSymbolNamesExtension

cpp_test_bad_identifiers.proto:113

(message has no fields)

message TestDeprecatedFields

unittest.proto:172

message TestDeprecatedLite

unittest_lite.proto:327

Test that deprecated fields work. We only verify that they compile (at one point this failed).

message TestDupFieldNumber

unittest.proto:411

Test that groups have disjoint field numbers from their siblings and parents. This is NOT possible in proto1; only proto2. When attempting to compile with proto1, this will emit an error; so we only include it in protobuf_unittest_proto.

NO_PROTO1

message TestDupFieldNumber.Bar

unittest.proto:414

Used in: TestDupFieldNumber

message TestDupFieldNumber.Foo

unittest.proto:413

Used in: TestDupFieldNumber

message TestDynamicExtensions

unittest.proto:624

Used by ExtensionSetTest/DynamicExtensions. The test actually builds a set of extensions to TestAllExtensions dynamically, based on the fields of this message type.

enum TestDynamicExtensions.DynamicEnumType

unittest.proto:625

Used in: TestDynamicExtensions

message TestDynamicExtensions.DynamicMessageType

unittest.proto:630

Used in: TestDynamicExtensions

message TestEagerMessage

unittest.proto:418

Additional messages for testing lazy fields.

message TestEmbedOptimizedForSize

unittest_embed_optimize_for.proto:45

message TestEmptyMessage

unittest.proto:369

TestEmptyMessage is used to test unknown field support.

(message has no fields)

message TestEmptyMessageWithExtensions

unittest.proto:374

Like above, but declare all field numbers as potential extensions. No actual extensions should ever be defined for this type.

(message has no fields)

enum TestEnumWithDupValue

unittest.proto:436

Test an enum that has multiple values with the same number.

message TestExtremeDefaultValues

unittest.proto:492

message TestFieldOrderings

unittest.proto:477

We list fields out of order, to ensure that we're using field number and not field index to determine serialization order.

message TestForeignNested

unittest.proto:364

Test that we can use NestedMessage from outside TestAllTypes.

message TestLazyMessage

unittest.proto:421

message TestLiteImportsNonlite

unittest_lite_imports_nonlite.proto:41

message TestMessageSet

unittest_mset.proto:42

A message with message_set_wire_format.

Used in: TestMessageSetContainer

(message has no fields)

message TestMessageSetContainer

unittest_mset.proto:47

message TestMessageSetExtension1

unittest_mset.proto:51

message TestMessageSetExtension2

unittest_mset.proto:58

message TestMessageWithCustomOptions

unittest_custom_options.proto:94

A test message with custom options at all possible locations (and also some regular options, to make sure they interact nicely).

enum TestMessageWithCustomOptions.AnEnum

unittest_custom_options.proto:102

message TestMultipleExtensionRanges

unittest.proto:378

(message has no fields)

message TestMutualRecursionA

unittest.proto:398

Test that mutual recursion works.

Used in: TestMutualRecursionB

message TestMutualRecursionB

unittest.proto:402

Used in: TestMutualRecursionA

message TestNestedExtension

unittest.proto:299

(message has no fields)

message TestNestedExtensionLite

unittest_lite.proto:319

(message has no fields)

message TestNestedMessageHasBits

unittest.proto:426

Needed for a Python test.

message TestNestedMessageHasBits.NestedMessage

unittest.proto:427

Used in: TestNestedMessageHasBits

message TestOptimizedForSize

unittest_optimize_for.proto:43

Used in: TestEmbedOptimizedForSize

message TestOptionalOptimizedForSize

unittest_optimize_for.proto:59

message TestPackedExtensions

unittest.proto:600

(message has no fields)

message TestPackedExtensionsLite

unittest_lite.proto:298

(message has no fields)

message TestPackedTypes

unittest.proto:564

message TestPackedTypesLite

unittest_lite.proto:166

message TestParsingMerge

unittest.proto:664

Test that if an optional or required message/group field appears multiple times in the input, they need to be merged.

message TestParsingMerge.OptionalGroup

unittest.proto:686

Used in: TestParsingMerge

message TestParsingMerge.RepeatedFieldsGenerator

unittest.proto:670

RepeatedFieldsGenerator defines matching field types as TestParsingMerge, except that all fields are repeated. In the tests, we will serialize the RepeatedFieldsGenerator to bytes, and parse the bytes to TestParsingMerge. Repeated fields in RepeatedFieldsGenerator are expected to be merged into the corresponding required/optional fields in TestParsingMerge.

message TestParsingMerge.RepeatedFieldsGenerator.Group1

unittest.proto:674

Used in: RepeatedFieldsGenerator

message TestParsingMerge.RepeatedFieldsGenerator.Group2

unittest.proto:677

Used in: RepeatedFieldsGenerator

message TestParsingMerge.RepeatedGroup

unittest.proto:689

Used in: TestParsingMerge

message TestParsingMergeLite

unittest_lite.proto:332

See the comments of the same type in unittest.proto.

message TestParsingMergeLite.OptionalGroup

unittest_lite.proto:349

Used in: TestParsingMergeLite

message TestParsingMergeLite.RepeatedFieldsGenerator

unittest_lite.proto:333

message TestParsingMergeLite.RepeatedFieldsGenerator.Group1

unittest_lite.proto:337

Used in: RepeatedFieldsGenerator

message TestParsingMergeLite.RepeatedFieldsGenerator.Group2

unittest_lite.proto:340

Used in: RepeatedFieldsGenerator

message TestParsingMergeLite.RepeatedGroup

unittest_lite.proto:352

Used in: TestParsingMergeLite

message TestReallyLargeTagNumber

unittest.proto:385

Test that really large tag numbers don't break anything.

message TestRecursiveMessage

unittest.proto:392

message TestRepeatedScalarDifferentTagSizes

unittest.proto:645

message TestRequired

unittest.proto:312

We have separate messages for testing required fields because it's annoying to have to fill in required fields in TestProto in order to do anything with it. Note that we don't need to test every type of required filed because the code output is basically identical to optional fields for all types.

Used in: TestRequiredForeign

message TestRequiredForeign

unittest.proto:357

message TestRequiredOptimizedForSize

unittest_optimize_for.proto:55

Used in: TestOptionalOptimizedForSize

enum TestSparseEnum

unittest.proto:446

Test an enum with large, unordered values.

Used in: SparseEnumMessage

message TestUnpackedTypes

unittest.proto:583

A message with the same fields as TestPackedTypes, but without packing. Used to test packed <-> unpacked wire compatibility.

message VariousComplexOptions

unittest_custom_options.proto:270

Note that we try various different ways of naming the same extension.

(message has no fields)