Class STNamedCodeTuples

java.lang.Object

io.nosqlbench.nb.spectest.testmodels.STNamedCodeTuples

public class STNamedCodeTuples
extends Object

This is a view over an STNodeAssembly, which is merely backed by a List of STNodes. This view, however, imposes a structure over the nodes which is name, data, name, data, ... and so on. This is a convenient way to consume and validate Node data which follows the form:

 *name1:*
 ```yaml
 document-property: version1
 ```
 *name2:*
 ```yaml
 document-property: version2
 ```
 *name3:*
 ```yaml
 document-property: version3
 ```
 

In this example, there are six consecutive nodes which contain 3 names and three fenced code sections.

Constructor Summary

Constructors

Constructor	Description
STNamedCodeTuples(List<STNameAndCodeTuple> tuples)

Method Summary

Modifier and Type	Method	Description
STNameAndCodeTuple	get(int i)
String	getTypeSignature()	For the STNamedCodeTuples view of a testable set of nodes, it is useful to see what the name structure looks like in order to conditionally match different types of testable sequences based on the asserted names in the documentation.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

STNamedCodeTuples

public STNamedCodeTuples(List<STNameAndCodeTuple> tuples)

Method Details

getTypeSignature

public String getTypeSignature()

For the STNamedCodeTuples view of a testable set of nodes, it is useful to see what the name structure looks like in order to conditionally match different types of testable sequences based on the asserted names in the documentation. This will return the named, concatenated with "->", and sanitized with all non-alphanumeric and > and $lt;, space, underscore and dash removed.

For the example structure at the class level, this would look like:

name1->name2->name3

Returns:

A signature of the node sequences based on the name elements

get

public STNameAndCodeTuple get(int i)