GET https://dev.normadoc.fr/_partial/product/IEEE00011396/features

Response
200 OK
IP
216.73.216.9
Profiled on
Token
548bbd

Components

3 Twig Components
5 Render Count
2 ms Render Time
172.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		2 0.51ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		2 1.44ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.22ms

Render calls

ProductState App\Twig\Components\ProductState 172.0 MiB 0.31 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#92625
  +product: App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 172.0 MiB 0.22 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#92803
  +product: App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Draft standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 172.0 MiB 0.69 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#92870
  +product: App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 172.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#99775
  +product: App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 172.0 MiB 0.75 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#99857
  +product: App\Entity\Product\Product {#7310
    #id: 13280
    #code: "IEEE00011396"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751041023 {#7274
      date: 2025-06-27 18:17:03.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753971079 {#7322
      date: 2025-07-31 16:11:19.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 48129
        #name: "IEEE P3407"
        #slug: "ieee-p3407-ieee00011396-571165"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard establishes the minimum s 1 et of requirements for end-to-end software testing automation tools. Also, this standard can be used to guide users and industries to prepare and perform different types of automated testing on software integration environments. These tools can help users and industries in streamlining the software test automation processes, leading to reducing cost and effort on test development, execution and maintenance.<br />\n
          \t\t\t\t<br />\n
          This standard addresses end-to-end software testing automation tools that are used to test end-to-end functionalities of the system in real software integration environments. These standardized tools are used to prepare and execute testing automation scripts faster to deliver high quality products by reducing the overhead on automation scripts preparation, maintenance, and execution. The end-to-end testing automation covers the testing of each layer of the application that includes functional / integration testing (Includes but not limited to user interface testing, application programming interface (API) testing, data flow and data testing, business logic testing, messaging testing, and visualization testing), performance testing and load testing. This standard also covers the grouping mechanisms of the test scenarios to group the scenarios in different categories like regression test, sanity test, smoke test, load test and with the ability to support custom tags so that the categorized test scenarios can be executed independently. The scope of this standard is to provide a minimum set of requirements for these tools.<br />\n
          Many industries are developing software testing automation scripts to verify end-to-end functionalities of the software applications on real integration environments. But the overhead and cost of automation scripts development, maintenance and execution are very high. The purpose of this standard is to set the minimum set of rules for the end-to-end testing automation tools from the perspective to reduce overall software testing cost by increasing the productivity and reducing the overhead on the automation scripts development, maintenance and execution. Overall, the purpose is to increase product quality and reduce product cost by reducing effort on product testing.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for End-to-End Software Testing Automation Tools"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1740697200 {#7292
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1740697200 {#7318
      date: 2025-02-28 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3407"
    -bookCollection: ""
    -pageCount: 66
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}