Parsing a string and counting characters.

If type1 is supposed to be 23 chars, then char 31 had better be "t"

in a similar fashion

char 44 should also be "t"

That would be the simplest way to check.  If you want the test to be more flexible, then you can parse the string and look for "type1" and then count some number of chars after that, then repeat that for each substring.

You can do any of the aqString functions in a keyword test using Run Code Snippet.

If you need help with either of these approaches, just ask!

If you have the Desktop module, you can use the .NET https://msdn.microsoft.com/en-us/library/ms150046(v=vs.110).aspx method to convert a query string into a name/value collection. Then you can get the parameter values as CollectionObj.Item(param_name). Note that to be able to use ParseQueryString, you need to add the System.Web assembly from the GAC to Tools > Current Project Properties > CLR Bridge.

Assuming you're using JScript, here's a sample function that shows how to use ParseQueryString and how to check the parameter length. You can call this function from your keyword tests using the Run Script Routine operation.

// JScript

/*
Usage example:

var str = "type1=12345678901234567890111&type2=3.0.00&type3=1234567811";
CheckQueryStringParameterLength(str, "type1", 23);
*/
function CheckQueryStringParameterLength(QueryString, ParamName, ExpectedLength)
{
  var qs = dotNET.System_Web.HttpUtility.ParseQueryString(QueryString);
  var strValue = qs.Item(ParamName).OleValue;

  var length = strValue.length;
  if (length == ExpectedLength)
    Log.Checkpoint(
      aqString.Format("Parameter \"%s\" has the correct length (%d).", ParamName, ExpectedLength),
      strValue
      );
  else {
    Log.Error(
      aqString.Format("Parameter \"%s\" is %d characters long, but should be %d characters.", ParamName, length, ExpectedLength),
      strValue
    );
  }
}