Requirements

Home > Requirements

Report generated 29-07-2023 17:16

Requirements Overview

Requirement Type	Total	Pass	Untested
Epics	18	18	0
Stories	24	23	1
Acceptance Criteria (tests)	171	171

Test Result Summary

Test Type	Total	Pass	Fail	Pending	Ignored
Automated	171	171 (100%)	0 (0%)	0 (0%)	0 (0%)
Manual	0	0 (0%)	0 (0%)	0 (0%)	0 (0%)
Total	171	171 (100%)	0 (0%)	0 (0%)	0 (0%)
Total Duration	23 seconds

Epics (18)

Epics

Stories

Automated
Tests

Manual
Tests

Test Results

Working Stories

Annotations

100%

50%

Basic types

100%

Class info

100%

Collections

100%

Constructors

100%

Data provider strategy

100%

Edge cases

100%

Extensions

100%

External factory

100%

Factories

100%

Inheritance

100%

Memoization

100%

Randomness

100%

Singletons

100%

Type manufacturing

100%

Validator framework

100%

Walk through example

100%

Xml types

100%

Acceptance Criteria

	Tests	Steps	Duration (seconds)
SUCCESS	Creating A Random Data Provider Strategy Should Create A Method Heavy Comparator	4	0.1
SUCCESS	Creating A Random Data Provider Strategy Should Create A Method Light Comparator	4	0.12
SUCCESS	Creating A Random Data Provider Strategy Should Create A Constructor Heavy Comparator	4	0.16
SUCCESS	Creating A Random Data Provider Strategy Should Create A Constructor Light Comparator	4	0.11
SUCCESS	Even When Memoization Is True, If Generics Pojos Have Different Types, Objects Should Not Be Equal	9	0.11
SUCCESS	In Presence Of Excluded Attributes, The Class Info Object Should Not Contain Those Attributes	5	0.13
SUCCESS	Invoking Podam On A POJO With A Circular Constructor (E.G. Java.Net.URL) Leads To A Null POJO	3	0.13
SUCCESS	Invoking Podam On A POJO With A Private, No Arguments Constructor, Should Return A Non Null POJO	4	0.11
SUCCESS	Invoking Podam On A POJO With Both Circular And Non Circular Constructors (E.G. Javax.Activation.Datahandler) Should Lead To A Non Empty POJO	3	0.12
SUCCESS	Invoking Podam On An Abstract Class Should Return A Null Pojo	3	0.13
SUCCESS	Invoking Podam On An Interface Should Return An Empty POJO	3	0.11
SUCCESS	Memoization Should Work Correctly For Collections And Arrays	15	0.12
SUCCESS	Memoization Should Work For Recursive Pojos	7	0.11
SUCCESS	Memoization Should Work With Generics	12	0.11
SUCCESS	Podam Messaging System Should Return A Byte Wrapped Value	5	0.1
SUCCESS	Podam Messaging System Should Return A Character Wrapped Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Double Wrapped Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Float Wrapped Value	5	0.12
SUCCESS	Podam Messaging System Should Return A Long Wrapped Value	5	0.12
SUCCESS	Podam Messaging System Should Return A Short Wrapped Value	5	0.11
SUCCESS	Podam Messaging System Should Return A String Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Boolean Primitive Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Boolean Wrapped Value	5	0.1
SUCCESS	Podam Messaging System Should Return A Byte Primitive Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Char Primitive Value	5	0.21
SUCCESS	Podam Messaging System Should Return A Double Primitive Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Float Primitive Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Long Primitive Value	5	0.11
SUCCESS	Podam Messaging System Should Return A Short Primitive Value	5	0.12
SUCCESS	Podam Messaging System Should Return An Enum Value	5	0.12
SUCCESS	Podam Messaging System Should Return An Int Primitive Value	5	0.1
SUCCESS	Podam Messaging System Should Return An Integer Value	5	0.11
SUCCESS	Podam Cannot Fill Interface Attributes If The External Factory Does Not Manufacture The Right Type	8	0.21
SUCCESS	Podam Cannot Instantiate Interfaces	10	0.12
SUCCESS	Podam Cannot Instantiate Interfaces Which Extend Map	10	0.13
SUCCESS	Podam Should Allow Validation Annotations Customization	8	0.12
SUCCESS	Podam Should Assign Exactly The Values Specified With The @Email Annotation	5	0.11
SUCCESS	Podam Should Assign Exactly The Values Specified With The @Podamstrategyvalue Annotation	30	0.2
SUCCESS	Podam Should Assign Precise Values And Lengths When A String Is Annotated With @Podamstringvalue	6	0.12
SUCCESS	Podam Should Be Able To Create An Abstract Class With Help Of Factory	4	0.13
SUCCESS	Podam Should Be Able To Create Instances Of Concurrent Hash Maps With Interface Values	4	0.12
SUCCESS	Podam Should Be Able To Create Instances Of Hash Maps With Interface Values	4	0.12
SUCCESS	Podam Should Be Able To Create Instances Of Jaxbelement	5	0.11
SUCCESS	Podam Should Be Able To Create Instances Of Jaxbelements Declared As Instance Variables In A POJO	6	0.12
SUCCESS	Podam Should Be Able To Create Instances Of Sorted Maps With Interface Values	4	0.11
SUCCESS	Podam Should Be Able To Create Instances Of Abstract Pojos With Factory Methods Which Return Concrete Types	3	0.1
SUCCESS	Podam Should Be Able To Create Instances Of Generic Pojos With Factory Methods When The Concrete Type Is Known	4	0.14
SUCCESS	Podam Should Be Able To Create Instances Of Generic Read Only Pojos With Factory Methods When The Concrete Type Is Known	4	0.11
SUCCESS	Podam Should Be Able To Create Instances Of Inner Classes	4	0.13
SUCCESS	Podam Should Be Able To Fill In Pojos With Jsonnullable Collection Wrapper	5	0.14
SUCCESS	Podam Should Be Able To Fill In Pojos With Raw Type Collection Attributes And Default Values To Object	6	0.13
SUCCESS	Podam Should Be Able To Find Attributes With Pattern [A-Z]	4	0.13
SUCCESS	Podam Should Be Able To Find Non-Standard Attributes With A Custom Class Info Strategy	4	0.15
SUCCESS	Podam Should Be Able To Fulfill Most Of The Javax Validation 2.0 Framework	8	0.11
SUCCESS	Podam Should Be Able To Fulfill Most Of The Javax Validation Framework	33	0.18
SUCCESS	Podam Should Be Able To Instantiate Pojos With Immutable Collections	3	0.11
SUCCESS	Podam Should Be Able To Instantiate Pojos With Immutable Maps	4	0.13
SUCCESS	Podam Should Be Able To Manufacture Pojos Which Contain Immutable Collections	9	0.11
SUCCESS	Podam Should Be Able To Manufacture Any Type Of Lists	5	0.13
SUCCESS	Podam Should Be Able To Manufacture Any Type Of Maps	4	0.12
SUCCESS	Podam Should Be Able To Manufacture Instances Of The Observable Class	3	0.11
SUCCESS	Podam Should Choose The Fullest Constructor When Invoked For Full Data	5	0.1
SUCCESS	Podam Should Choose The Lightest Constructor When The Standard Manufacturing Method Is Invoked	5	0.15
SUCCESS	Podam Should Correctly Generate Hashmaps With Long As Key Type	5	0.11
SUCCESS	Podam Should Correctly Handle Generic Collections In Constructor With Memoization Disabled	9	0.11
SUCCESS	Podam Should Correctly Handle Generic Collections In Constructor With Memoization Enabled	11	0.14
SUCCESS	Podam Should Create Inputstream With The Custom Type Manufacturer	7	0.12
SUCCESS	Podam Should Create Pojos In Accordance With Custom Data Provider Strategies	13	0.1
SUCCESS	Podam Should Create Pojos In Accordance With Custom Data Provider Strategies	13	0.16
SUCCESS	Podam Should Create Timestamp With The Custom Type Manufacturer	4	0.12
SUCCESS	Podam Should Create An Instance Of An Abstract Class With A Factory Method Which Returns A Concrete Type Even If The Concrete Type Has Got Read-Only Attributes. These Will Be Empty.	3	0.14
SUCCESS	Podam Should Create Instances Of Pojos Extending Generic Classes	6	0.18
SUCCESS	Podam Should Create Instances Of Pojos Extending Generic Classes With Matching Generic Placeholders	5	0.13
SUCCESS	Podam Should Fill Attributemetadata With The Attribute Name	8	0.14
SUCCESS	Podam Should Fill Charsequence Type	4	0.13
SUCCESS	Podam Should Fill Java Native Types	9	0.12
SUCCESS	Podam Should Fill Java String Type	3	0.15
SUCCESS	Podam Should Fill Java String Type With Full Constructor	3	0.14
SUCCESS	Podam Should Fill Pojos And Interface Attributes If A Full Constructor Sets The Interface Attribute Value	9	0.11
SUCCESS	Podam Should Fill Pojos With Non Default Constructors	3	0.14
SUCCESS	Podam Should Fill Pojos With Protected, Non Default Constructors	5	0.11
SUCCESS	Podam Should Fill Pojos With Public, Non Default Constructors	5	0.12
SUCCESS	Podam Should Fill Array When Invoking The Factory Population Directly	3	0.16
SUCCESS	Podam Should Fill Arrays With Elements	4	0.12
SUCCESS	Podam Should Fill Embedded Abstract Classes If A Concrete Type Has Been Specified	5	0.12
SUCCESS	Podam Should Fill In Maps Of The Containing Class Type	4	0.15
SUCCESS	Podam Should Fill In Pojos Which Contain Internal Loops (E.G. Objects That Reference Parents)	3	0.13
SUCCESS	Podam Should Fill In Pojos Which Have A Circular Dependency	9	0.15
SUCCESS	Podam Should Fill In Pojos Which Have A Circular Dependency And Custom Depth	10	0.14
SUCCESS	Podam Should Fill In Pojos With Enums	6	0.11
SUCCESS	Podam Should Fill In Pojos With Attributes Containing Wildcards	6	0.12
SUCCESS	Podam Should Fill In A POJO With Basic Jvm Types	6	0.13
SUCCESS	Podam Should Fill In Complex (E.G. With More Than Two Generic Types), Read-Only Pojos	8	0.11
SUCCESS	Podam Should Fill In Lists Of The Containing Class Type	5	0.22
SUCCESS	Podam Should Fill In Read-Only Pojos	9	0.13
SUCCESS	Podam Should Fill In The Address POJO Correctly	4	0.12
SUCCESS	Podam Should Fill In The Bank Account POJO Correctly	3	0.12
SUCCESS	Podam Should Fill In The Country POJO Correctly	3	0.13
SUCCESS	Podam Should Fill In The Order POJO Correctly	13	0.12
SUCCESS	Podam Should Fill In Wildcard Enum Fields	4	0.13
SUCCESS	Podam Should Fill Recursive Pojos Correctly, Including All Their Fields	4	0.13
SUCCESS	Podam Should Fill Recursive Pojos Correctly, Including All Their List Fields	17	0.16
SUCCESS	Podam Should Fill Recursive Pojos When Invoking The Factory Population Directly	3	0.13
SUCCESS	Podam Should Fill The Article POJO Correctly	3	0.11
SUCCESS	Podam Should Fill The Client POJO Correctly	49	0.14
SUCCESS	Podam Should Fill The Orderitem POJO Correctly	4	0.12
SUCCESS	Podam Should Fill Values Invoking Children Setters Accepting A Type Different From The Parent Type	3	0.12
SUCCESS	Podam Should Generate A Classinfo Which Contains Information For The Setters Contained In The POJO	4	0.14
SUCCESS	Podam Should Generate A Non Null POJO For Abstract Types With A Concrete Type	7	0.13
SUCCESS	Podam Should Generate Evenly Distributed Random Integers	1	0.15
SUCCESS	Podam Should Handle Pojos With Annotated Field And Setter	5	0.11
SUCCESS	Podam Should Handle POJOs With Constructors That Have One Or More Self References To The POJO Class, Provided The Required Constructor Is Annotated With @Podamconstructor	5	0.14
SUCCESS	Podam Should Handle Pojos With Multiple Annotated Fields And Custom Generic Annotation Strategy	24	0.11
SUCCESS	Podam Should Handle Pojos With Multiple Annotated Fields, Ignoring Any Non Podam Annotation	7	0.15
SUCCESS	Podam Should Handle Pojos With No Setters And Collections In The Constructor	12	0.2
SUCCESS	Podam Should Handle Pojos With Private Constructors Only	5	0.11
SUCCESS	Podam Should Handle Pojos With Self Reference Constructors But Not Default Constructors Without The Need For The @Podamconstructor Annotation	5	0.11
SUCCESS	Podam Should Handle Singletons With Parameters In The Static Method	8	0.13
SUCCESS	Podam Should Handle Attributes In Accordance With Custom Class Info Strategies	7	0.15
SUCCESS	Podam Should Handle Basic Inheritance Scenarios	7	0.13
SUCCESS	Podam Should Handle Booleans Correctly	11	0.17
SUCCESS	Podam Should Handle Both Native And Wrapped Boolean Values With @Podambooleanvalue Annotation	9	0.13
SUCCESS	Podam Should Handle Both Native And Wrapped Byte Values With @Podambytevalue Annotation	13	0.12
SUCCESS	Podam Should Handle Both Native And Wrapped Char Values With @Podamcharvalue Annotation	13	0.11
SUCCESS	Podam Should Handle Both Native And Wrapped Double Values With @Podamdoublevalue Annotation	9	0.12
SUCCESS	Podam Should Handle Both Native And Wrapped Float Values With @Podamfloatvalue Annotation	15	0.11
SUCCESS	Podam Should Handle Both Native And Wrapped Integer Values With @Podamintvalue Annotation	15	0.18
SUCCESS	Podam Should Handle Both Native And Wrapped Long Values With @Podamlongvalue Annotation	15	0.13
SUCCESS	Podam Should Handle Both Native And Wrapped Short Values With @Podamshortvalue Annotation	13	0.13
SUCCESS	Podam Should Handle Classes With Generic Key/Value Types	4	0.12
SUCCESS	Podam Should Handle Classes With Read Only Maps Having Same Key And Value Types	4	0.15
SUCCESS	Podam Should Handle Constructors With Generic Arrays During Pojo Instantiation	4	0.11
SUCCESS	Podam Should Handle Constructors With Multiple Generics During Pojo Instantiation	7	0.13
SUCCESS	Podam Should Handle Generics In Setters During Pojo Instantiation	5	0.13
SUCCESS	Podam Should Handle Generics In Static Constructors During POJO Instantiation	5	0.11
SUCCESS	Podam Should Handle Generics In The Constructor	5	0.13
SUCCESS	Podam Should Handle Immutable Pojos Annotated With @Podamconstructor	8	0.16
SUCCESS	Podam Should Handle Immutable Pojos With Generified Collections In The Constructor	13	0.13
SUCCESS	Podam Should Handle Immutable Pojos With Non Generic Collections	13	0.13
SUCCESS	Podam Should Handle Immutable Non Annotated Pojos	8	0.16
SUCCESS	Podam Should Handle Optional List Of Strings	6	0.12
SUCCESS	Podam Should Handle Standard Collections	33	0.18
SUCCESS	Podam Should Handle The Manufacturing Of Pojos Which Inherit From Other Classes	5	0.11
SUCCESS	Podam Should Handle The Manufacturing Of Pojos With Generic Types In Constructor	5	0.14
SUCCESS	Podam Should Handle The Manufacturing Of Basic Types	5	0.11
SUCCESS	Podam Should Handle The Manufacturing Of Generic Pojos	5	0.11
SUCCESS	Podam Should Manufacture All Pojos In A Tree Hierarchy	5	0.12
SUCCESS	Podam Should Manufacture Attributes Implementing Collection And Map Interfaces	12	0.13
SUCCESS	Podam Should Manufacture Package Private Pojos	4	0.13
SUCCESS	Podam Should Not Be Able To Create Instances Of An Abstract Class Even If The POJO Has A Full Constructor	8	0.13
SUCCESS	Podam Should Not Be Able To Create Instances Of An Abstract Class If The External Factory Does Not Provide A Concrete Implementation	8	0.13
SUCCESS	Podam Should Not Create Instances Of An Interface When Given An External Factory Which Does Not Manufacture The Concrete Type	8	0.11
SUCCESS	Podam Should Not Create Instances Of Non-Instantiable Classes	8	0.12
SUCCESS	Podam Should Not Fill POJO'S Attributes Annotated With @Podamexclude	5	0.68
SUCCESS	Podam Should Return A Null Value For Non Instantiable Pojos	3	0.11
SUCCESS	Podam Should Return Valid Class Info For Pojos With No Attributes	3	0.13
SUCCESS	Podam Should Throw An Exception If A POJO Contains Invalid Getters Or Setters	1	0.11
SUCCESS	Podam Will Create An Instance Of A POJO But Its Interface Types Won'T Be Instantiated	10	0.12
SUCCESS	The @Podamcollection Annotation Should Allow To Set Sizes On All Collections And Arrays	11	0.11
SUCCESS	The Classinfo Object Created For A Class Should Handle @Podamexcludeannotations	4	0.13
SUCCESS	The Random Data Provider Strategy Should Be Initialised Correctly And Allow For Changes In The Number Of Collection Elements	3	0.12
SUCCESS	The Management Of External Factories Should Be Correct And Chaining Should Work	7	0.12
SUCCESS	When Given An External Factory, Podam Should Be Able To Create Instances Of Xmlgregoriancalendar	3	0.11
SUCCESS	When Given An External Factory, Podam Should Be Able To Create Instances Of The Duration Class	3	0.14
SUCCESS	When Given An External Factory, Podam Should Be Able To Fill Pojos With Instance Attributes Containing Xmlgregoriancalendar And Duration	5	0.11
SUCCESS	When Memoization Cache Is Cleared Then Objects Should Not Be Equal	13	0.12
SUCCESS	When Memoization Is Set To False Podam Should Return Different Instances For Different Invocations	7	0.12
SUCCESS	When Memoization Is Set To True Podam Should Return The Same Instance For Different Invocations	9	0.11
SUCCESS	When The @Digits And @Decimalmin And @Decimalmax Applied To The Same Field, Podam Should Use Minimum Requirements	5	0.36
SUCCESS	When The @Size Annotation Doesn'T Have A Max Length Specified, Podam Should Assign A Sensible Value	6	0.12
SUCCESS	When The Annotationstrategy And The Typemanufacturer Are Specified, The Former Has Precedence	9	0.13