@prathmesh4321 please try this implementation for

buildtest bc find -t
buildtest bc find -e
buildtest bc find -b

this is not relevant for -p since its just paths to root of buildspecs.

I dont think it makes sense to have --row-count for --group-by-tags and --group-by-executor

I am not sure if its useful to know total number of filter fields and format fields, if its important then potentially we add support with option --filterfields and --formatfields

@prathmesh4321 please try this implementation for

buildtest bc find -t
buildtest bc find -e
buildtest bc find -b

this is not relevant for -p since its just paths to root of buildspecs.

I dont think it makes sense to have --row-count for --group-by-tags and --group-by-executor

I am not sure if its useful to know total number of filter fields and format fields, if its important then potentially we add support with option --filterfields and --formatfields

@shahzebsiddiqui Okay, I have added --row-count option for "buildtest bc find -t", "buildtest bc find -e", "buildtest bc find -b". I don't think its useful to add --row-count option for --filterfields and --formatfields.

Rather than adding this as an option to all of your print functions I would consider instead checking for the argument in the main function and than printing the table there since all of the code is the same, but copied to different places.

@jscook2345 so you want a top level argument buildtest --row-count instead of implementing it in the subcommands.

Currently this is present in buildtest report and buildtest buildspec find.

I thought about it when there is redundancy I think it does make sense to move this to top level argument.