--- title: Test Plan and Methodology Design for Network Equipment Acceptance | TEST4NET description: "A written test plan and methodology for network and security equipment acceptance: cases, pass criteria, topology and report format, drafted by TEST4NET and signed off by you. First draft from 3 business days." image: https://test4net.com/hubfs/og/services-test-plan-design.png --- [Skip to content](https://test4net.com/services/test-plan-design#main-content) [![TEST4NET](https://test4net.com/hubfs/test4net-logo-fixed-2.svg)](https://test4net.com/?hsLang=en) - Services - Products - Resources - Company [News](https://test4net.com/news?hsLang=en) [Login](https://lab.test4net.com) [Support](https://test4net.com/support?hsLang=en) What we test By technology Industries [Load & Performance Testing Throughput, sessions and latency up to and past the rated limit](https://test4net.com/services/load-performance-testing?hsLang=en) [Functional & Conformance Testing Features against the spec, RFC compliance with evidence](https://test4net.com/services/functional-conformance-testing?hsLang=en) [Interoperability Testing Multi-vendor behaviour, before it reaches production](https://test4net.com/services/interoperability-testing?hsLang=en) [Security & Resilience Testing NGFW, IPS and VPN efficacy and performance with threats on the wire](https://test4net.com/services/security-resilience-testing?hsLang=en) [Test Plan & Methodology Design What to test, how, and what counts as a pass](https://test4net.com/services/test-plan-design?hsLang=en) [Test Automation & CI/CD Regression suites wired into your release pipeline](https://test4net.com/services/test-automation?hsLang=en) [Training Programs Hands-on courses for your test engineers](https://test4net.com/services#training) [Equipment Repair Diagnostics and repair of test equipment](https://test4net.com/services#repair) [All services](https://test4net.com/services?hsLang=en) [Routing & Switching RFC 2544 and RFC 2889 on real ports, 1G to 100G](https://test4net.com/solutions/routing-switching?hsLang=en) [Firewalls & NGFW RFC 9411 throughput with inspection switched on](https://test4net.com/solutions/firewalls-ngfw?hsLang=en) [SD-WAN & WAN Path selection and QoS under emulated WAN conditions](https://test4net.com/solutions/sd-wan?hsLang=en) [Cloud & NFV Virtual appliances and cloud services under load](https://test4net.com/solutions/cloud-nfv?hsLang=en) [5G & Mobile Core Transport and core functions under subscriber traffic](https://test4net.com/solutions/5g-mobile-core?hsLang=en) [Wi-Fi Wi-Fi 6 clients and access points, Wi-Fi 7 in progress](https://test4net.com/solutions/wi-fi?hsLang=en) [Storage & Infrastructure Storage networks and servers under realistic I/O](https://test4net.com/solutions/storage?hsLang=en) [AI / Switching Fabric (RoCEv2) Lossless Ethernet for GPU clusters: PFC, ECN, fabric load](https://test4net.com/solutions/ai-fabric-rocev2?hsLang=en) [All technologies](https://test4net.com/services#coverage) [Telecom Operators Pre-deployment acceptance and vendor comparison](https://test4net.com/solutions/industries#telecom) [Network & Security Vendors Independent validation of your product claims](https://test4net.com/solutions/industries#vendors) [System Integrators Proof for the customer before the rollout](https://test4net.com/solutions/industries#integrators) [Enterprise & Banks Upgrades and new platforms checked before production](https://test4net.com/solutions/industries#enterprise) [All industries](https://test4net.com/solutions/industries?hsLang=en) Not sure where to start? Test plan and quote in 1–3 business days Tell us what you run and what worries you. We propose the tests, tools and timeline. [Request a test plan](https://test4net.com/contacts?hsLang=en) CloudLAB [How It Works Pick a scenario, run it in the live lab, get the report](https://test4net.com/cloudlab#how) [Equipment & Capabilities L2-3 to 100G, L4-7 past 200G, Wi-Fi, WAN emulation](https://test4net.com/cloudlab#equipment) [Access Plans Hourly sessions, subscriptions, dedicated racks](https://test4net.com/cloudlab/plans?hsLang=en) [Hosted DUT Testing Ship the box or upload the VM, we run the tests](https://test4net.com/cloudlab/hosted-dut?hsLang=en) [Open the CloudLAB portal](https://lab.test4net.com) Our tools [Traffic Generator L4-7 and security traffic past 200 Gbit/s, app mix library](https://test4net.com/products/traffic-generator?hsLang=en) [WANemu Delay, jitter, loss and bandwidth shaping per link](https://test4net.com/products/wanemu?hsLang=en) [Book a demo](https://test4net.com/contacts?hsLang=en) New: our own test tools Our own tools, in beta this autumn Built in our lab, priced per gigabit. Join the beta list and see them first. [Join the beta list](https://test4net.com/products#lead-form) Read Technologies / Protocols Methodologies [Blog Case studies, test insights and lab notes](https://test4net.com/blog?hsLang=en) [Industry News What is changing in network testing and infrastructure](https://test4net.com/news?hsLang=en) [FAQ How the lab, sessions and reports work](https://test4net.com/faq?hsLang=en) [All resources](https://test4net.com/resources?hsLang=en) [BGP Route exchange, policy and convergence](https://test4net.com/blog/how-we-test-bgp?hsLang=en) [OSPF & IS-IS IGP adjacency, flooding and SPF timing](https://test4net.com/blog/how-we-test-ospf-is-is?hsLang=en) [MPLS & SR LDP, RSVP‑TE and SR‑MPLS label paths](https://test4net.com/blog/how-we-test-mpls-and-segment-routing?hsLang=en) [EVPN / VXLAN Overlay fabrics, MAC/IP routes, multi-homing](https://test4net.com/blog/how-we-test-evpn-vxlan?hsLang=en) [IPsec & IKEv2 Tunnel setup, rekeying and throughput](https://test4net.com/blog/how-we-test-ipsec-and-ikev2?hsLang=en) [TLS / HTTPS Handshakes, cipher suites and inspection](https://test4net.com/blog/how-we-test-tls-and-https?hsLang=en) [RoCEv2 Lossless Ethernet, PFC and ECN for AI fabrics](https://test4net.com/blog/how-we-test-rocev2?hsLang=en) [Wi-Fi 6 / 6E / 7 802.11ax/be, OFDMA, MLO and roaming](https://test4net.com/blog/how-we-test-wi-fi-6-6e-7?hsLang=en) [All protocols](https://test4net.com/blog/tag/protocols?hsLang=en) [RFC 2544 Throughput, latency, frame loss and back-to-back](https://test4net.com/methodologies/rfc-2544?hsLang=en) [RFC 2889 LAN switch benchmarking: forwarding, MAC learning, congestion](https://test4net.com/methodologies/rfc-2889?hsLang=en) [RFC 9411 / RFC 3511 Firewall and NGFW performance benchmarking](https://test4net.com/methodologies/rfc-9411-rfc-3511?hsLang=en) [RFC 6349 TCP throughput and buffer delay testing](https://test4net.com/methodologies/rfc-6349?hsLang=en) [RFC 5180 IPv6 benchmarking methodology](https://test4net.com/methodologies/rfc-5180?hsLang=en) [ITU-T Y.1564 Ethernet service activation: CIR, EIR, KPIs per service](https://test4net.com/methodologies/y-1564?hsLang=en) [ITU-T Y.1731 Ethernet OAM: delay, jitter, loss and SLA monitoring](https://test4net.com/methodologies/y-1731?hsLang=en) [TR-398 Wi-Fi in-premises performance test plan](https://test4net.com/methodologies/tr-398?hsLang=en) [All methodologies](https://test4net.com/methodologies?hsLang=en) Read [Case studies, test insights and lab notes Blog](https://test4net.com/blog?hsLang=en) [What is changing in network testing and infrastructure Industry News](https://test4net.com/news?hsLang=en) [How the lab, sessions and reports work FAQ](https://test4net.com/faq?hsLang=en) [About Us Independent lab in Armenia, team and history](https://test4net.com/about?hsLang=en) [Why TEST4NET What you get that vendor slides never show](https://test4net.com/why-test4net?hsLang=en) [Lab & Certifications Bench capacity, methods and the standards we test against](https://test4net.com/lab?hsLang=en) [Partners Test tool vendors and IT partners we work with](https://test4net.com/partners?hsLang=en) [Contacts Talk to an engineer, not a sales bot](https://test4net.com/contacts?hsLang=en) [Support portal](https://test4net.com/support?hsLang=en) - Services What we test [Load & Performance Testing](https://test4net.com/services/load-performance-testing?hsLang=en) [Functional & Conformance Testing](https://test4net.com/services/functional-conformance-testing?hsLang=en) [Interoperability Testing](https://test4net.com/services/interoperability-testing?hsLang=en) [Security & Resilience Testing](https://test4net.com/services/security-resilience-testing?hsLang=en) [Test Plan & Methodology Design](https://test4net.com/services/test-plan-design?hsLang=en) [Test Automation & CI/CD](https://test4net.com/services/test-automation?hsLang=en) [Training Programs](https://test4net.com/services#training) [Equipment Repair](https://test4net.com/services#repair) [All services](https://test4net.com/services?hsLang=en) By technology [Routing & Switching](https://test4net.com/solutions/routing-switching?hsLang=en) [Firewalls & NGFW](https://test4net.com/solutions/firewalls-ngfw?hsLang=en) [SD-WAN & WAN](https://test4net.com/solutions/sd-wan?hsLang=en) [Cloud & NFV](https://test4net.com/solutions/cloud-nfv?hsLang=en) [5G & Mobile Core](https://test4net.com/solutions/5g-mobile-core?hsLang=en) [Wi-Fi](https://test4net.com/solutions/wi-fi?hsLang=en) [Storage & Infrastructure](https://test4net.com/solutions/storage?hsLang=en) [AI / Switching Fabric (RoCEv2)](https://test4net.com/solutions/ai-fabric-rocev2?hsLang=en) [All technologies](https://test4net.com/services#coverage) Industries [Telecom Operators](https://test4net.com/solutions/industries#telecom) [Network & Security Vendors](https://test4net.com/solutions/industries#vendors) [System Integrators](https://test4net.com/solutions/industries#integrators) [Enterprise & Banks](https://test4net.com/solutions/industries#enterprise) [All industries](https://test4net.com/solutions/industries?hsLang=en) [Not sure where to start? Test plan and quote in 1–3 business days](https://test4net.com/contacts?hsLang=en) - Products CloudLAB [How It Works](https://test4net.com/cloudlab#how) [Equipment & Capabilities](https://test4net.com/cloudlab#equipment) [Access Plans](https://test4net.com/cloudlab/plans?hsLang=en) [Hosted DUT Testing](https://test4net.com/cloudlab/hosted-dut?hsLang=en) [Open the CloudLAB portal](https://lab.test4net.com) Our tools [Traffic Generator](https://test4net.com/products/traffic-generator?hsLang=en) [WANemu](https://test4net.com/products/wanemu?hsLang=en) [Book a demo](https://test4net.com/contacts?hsLang=en) [New: our own test tools Our own tools, in beta this autumn](https://test4net.com/products#lead-form) - Resources Read [Blog](https://test4net.com/blog?hsLang=en) [Industry News](https://test4net.com/news?hsLang=en) [FAQ](https://test4net.com/faq?hsLang=en) [All resources](https://test4net.com/resources?hsLang=en) Technologies / Protocols [BGP](https://test4net.com/blog/how-we-test-bgp?hsLang=en) [OSPF & IS-IS](https://test4net.com/blog/how-we-test-ospf-is-is?hsLang=en) [MPLS & SR](https://test4net.com/blog/how-we-test-mpls-and-segment-routing?hsLang=en) [EVPN / VXLAN](https://test4net.com/blog/how-we-test-evpn-vxlan?hsLang=en) [IPsec & IKEv2](https://test4net.com/blog/how-we-test-ipsec-and-ikev2?hsLang=en) [TLS / HTTPS](https://test4net.com/blog/how-we-test-tls-and-https?hsLang=en) [RoCEv2](https://test4net.com/blog/how-we-test-rocev2?hsLang=en) [Wi-Fi 6 / 6E / 7](https://test4net.com/blog/how-we-test-wi-fi-6-6e-7?hsLang=en) [All protocols](https://test4net.com/blog/tag/protocols?hsLang=en) Methodologies [RFC 2544](https://test4net.com/methodologies/rfc-2544?hsLang=en) [RFC 2889](https://test4net.com/methodologies/rfc-2889?hsLang=en) [RFC 9411 / RFC 3511](https://test4net.com/methodologies/rfc-9411-rfc-3511?hsLang=en) [RFC 6349](https://test4net.com/methodologies/rfc-6349?hsLang=en) [RFC 5180](https://test4net.com/methodologies/rfc-5180?hsLang=en) [ITU-T Y.1564](https://test4net.com/methodologies/y-1564?hsLang=en) [ITU-T Y.1731](https://test4net.com/methodologies/y-1731?hsLang=en) [TR-398](https://test4net.com/methodologies/tr-398?hsLang=en) [All methodologies](https://test4net.com/methodologies?hsLang=en) Read [Blog Case studies, test insights and lab notes](https://test4net.com/blog?hsLang=en) [Industry News What is changing in network testing and infrastructure](https://test4net.com/news?hsLang=en) [FAQ How the lab, sessions and reports work](https://test4net.com/faq?hsLang=en) - Company [About Us](https://test4net.com/about?hsLang=en) [Why TEST4NET](https://test4net.com/why-test4net?hsLang=en) [Lab & Certifications](https://test4net.com/lab?hsLang=en) [Partners](https://test4net.com/partners?hsLang=en) [Contacts](https://test4net.com/contacts?hsLang=en) [News](https://test4net.com/news?hsLang=en) [Login](https://lab.test4net.com) [Support](https://test4net.com/support?hsLang=en) [Services](https://test4net.com/services?hsLang=en) / Test plan and methodology design # A test plan the vendor signs and your lab can run We write the document that decides a tender, an acceptance or your own lab routine: what to test, on which topology and traffic, in what order, and what counts as a pass. Traffic profiles come from your network, pass criteria carry a load level and a duration, every test case names its evidence. The vendor reviews it before the first packet, so the result cannot be argued away afterwards. First draft from 3 business days. You run it in your lab, the vendor runs it in theirs, or we run it in CloudLAB. [Request a plan](https://test4net.com/services/test-plan-design#lead-form) [What the document contains](https://test4net.com/services/test-plan-design#parts) **Acceptance test plan, core switching** Structure of a typical document. 6 parts, 11 test cases. 1. 1 Scope and devices 2. 2 Topology and bench 3. 3 Traffic profiles 4. 4 Test cases and KPIs 5. 5 Pass criteria 6. 6 Report and evidence TC-07 Latency under 70% load, 9000-byte frames p99 ≤ 12 µs for 300 s Signed before the run Customer Vendor - **From 3 days**to the first draft - **6 parts**one document, one scope - **1 review round**with you and the vendor, included - **20 years**in test labs behind every plan From your network to the traffic profile in the plan NetFlow, 7 days or a pcap sample Breakdown protocols · frame sizes · peaks Storage 41% HTTPS 27% Video 18% Voice 6% Other 8% Plan profile mix · sizes · ramp 41%9000 B 27%1400 B 18%1200 B 6%200 B 8%IMIX Why not the vendor’s plan ## Three places where a borrowed test plan loses the tender for you Most acceptance plans are a vendor template with the customer’s logo on it. They test what the box is good at, on traffic that never ran in your network, against a criterion nobody can fail. 1. ### The traffic is not yours 64-byte frames and a flat IMIX say nothing about a network that carries 9000-byte storage flows and TLS 1.3. We take 7 days of NetFlow or a pcap sample and turn it into the profile the plan uses. 2. ### The criterion has no load and no clock «Latency under 20 µs» passes on an idle box. «p99 latency under 12 µs at 70% of line rate for 300 s with 9000-byte frames» passes or fails, and the number is in the report either way. 3. ### The failure cases are missing Link loss with 500,000 BGP routes, an upgrade with traffic, a full log queue: the cases that hurt in production are the ones the template leaves out. We put them in and agree the pass criterion in advance. Inside the document ## Six parts, each with a source and an owner The plan is one document with six parts. Every part says where its content comes from and who signs it off, so the vendor cannot later call the setup unfair and your team cannot lose a page in e-mail. | Part | What it contains | Where it comes from | Who signs it off | | --- | --- | --- | --- | | 01Scope and devices | Models, firmware, licences, roles in the network, what is out of scope | Your tender or device list | You | | 02Topology and bench | Wiring, port map, generator ports, management access, who provides what | Your network diagram, our bench | You and the vendor | | 03Traffic profiles | Mix in percent, frame sizes, sessions, ramp and sustain, attack sets where relevant | Your NetFlow or pcap, RFC mixes | You | | 04Test cases and KPIs | ID, objective, procedure step by step, the KPIs sampled and how often | RFC 2544, 2889, 3511, 9411, Y.1564, TR-398 and your own cases | Our engineer | | 05Pass criteria | A number, a load level, a duration and a frame size for every case | Your SLA and capacity plan | You and the vendor | | 06Report and evidence | Result table template, evidence list per case, retest rules | Our report format | You | Where a published methodology applies, the plan cites it by section and says what is changed and why. Where none applies, the case is written from scratch and marked as such. How it is written ## Five steps, the vendor at the table before the run 1. 1 ### Brief 1 call The decision the plan has to support, the devices, the deadline, who will run the tests Scope and quote in 1 business day 2. 2 ### Inputs Day 1 Tender text, network diagram, device list, a NetFlow export or a pcap sample, your SLA Checklist of inputs, one page 3. 3 ### Draft Days 1–3 The six parts, every test case with its pass criterion, traffic profiles built from your data First draft from 3 days 4. 4 ### Review Days 3–5 One round with your team and the vendor. Every comment is logged with what changed and what was refused and why. Signed version with a change log 5. 5 ### Run Your choice Your lab runs it, the vendor runs it under your eyes, or we run it in CloudLAB and hand over the report Report in the plan’s own template Typical scenario ## Four equal datasheets, one tender, two lines in the plan decide it A bank buys 40 core switches. Four vendors, four datasheets with the same throughput. The plan has 11 test cases built on the bank’s own traffic: 41% storage flows with 9000-byte frames and a nightly peak. Two cases decide the outcome: latency at 70% load with jumbo frames and a link loss with 500,000 BGP routes. Two of the four candidates fail them, one passes with a note, one passes clean. The bank buys the clean one and keeps the plan as its acceptance routine for every firmware since. 11 cases written in 4 business days 2 of 4 candidates failed the two cases that mattered 1 plan reused for every firmware acceptance since Composite scenario from projects of this type. Numbers are realistic and not from one client. Result grid, 5 of 11 cases ABCD TC-03 Throughput, your mix TC-07 Latency, 70% load, 9000 B TC-08 Link loss, 500k BGP routes TC-10 Upgrade with traffic TC-11 Log storm PassPass with a noteFail One test case ## What a test case looks like on the page Every case has the same card, whoever runs it. An engineer who has never seen the bench can execute it from the card alone, and the vendor can repeat it in their own lab and get the same number. Four rules for the pass criterion, applied to every case in the plan A number Not «acceptable latency» but «p99 ≤ 12 µs». If the SLA has no number yet, we derive one from the capacity plan and mark it as derived. A load Every criterion names the load it holds at: percent of line rate, sessions, routes, tunnels. Idle results are recorded but never count. A clock Sustain time and sampling interval are in the case. 300 s of sustain and a 2 s sample is the default for performance cases. An evidence list What proves the result: generator statistics, device counters, captures, console log. The report is incomplete until all of it is attached. TC-07 Performance Pass criterion ### Latency under 70% load with 9000-byte frames Objective Confirm that storage traffic keeps its latency budget on the core switch while the uplinks carry the nightly peak Traffic Profile P2 (storage 41%, HTTPS 27%, video 18%, voice 6%, other 8%), 9000-byte frames on the storage share, ramp 60 s, sustain 300 s at 70% of line rate on all 32 ports KPIs Latency p50, p99 and max per port pair, frame loss, sampled every 2 s Pass criterion p99 ≤ 12 µs and loss 0 on every port pair for the full 300 s. One excursion above 12 µs is a pass with a note; loss is a fail. Evidence Generator latency histogram per pair, switch interface counters before and after, a capture of 60 s on two pairs Who writes it ## Written by the engineers who run the bench, not by a sales team The author of the plan is the engineer who would run it in CloudLAB: 20 years in vendor and operator test labs, RFC 2544, 2889, 3511 and 9411, Y.1564 and TR-398 in daily use. The plan is written for the tools you have, from a commercial generator to TRex and iperf, and says which cases need which tool. If you want us to run it, the bench carries 200 Gbps and more and the report comes in the plan’s own template. [Bench access and capacity](https://test4net.com/services#bench) [Run it as a load and performance test](https://test4net.com/services/load-performance-testing?hsLang=en) [RFC 2544 and 2889 on our bench](https://test4net.com/methodologies/rfc-2544?hsLang=en) [RFC 9411 for firewalls](https://test4net.com/methodologies/rfc-9411-rfc-3511?hsLang=en) ### Related reading - [BlogWhy vendor benchmarks are not enough for infrastructure decisions](https://test4net.com/blog/datasheet?hsLang=en) - [BlogSONiC passes 5 billion dollars: the acceptance test is still on the buyer](https://test4net.com/blog/sonic-5-billion-2026-white-box-acceptance-on-buyer?hsLang=en) - [BlogHow to run a security product test you can trust](https://test4net.com/blog/how-to-run-a-security-product-test-you-can-actually-trust?hsLang=en) Questions before the brief ## What buyers ask first What do you need from us to start? The tender text or the decision the plan supports, a network diagram, the device list with firmware, a NetFlow export or a pcap sample of a typical week, and your SLA or capacity plan if there is one. Missing items are replaced by stated assumptions in the draft. Can the vendor dispute the plan? They are meant to, before the run. One review round with the vendor is included. Every comment is logged with what changed or why it was refused, and the signed version carries that log. Is it written for the tools we already have? Yes. The plan names the tool class per case: a commercial generator for line-rate and latency cases, TRex or iperf where they are enough, a protocol emulator for routes and tunnels. If a case cannot be run with your tools, the plan says so and offers CloudLAB for that case. Which standards does it follow? RFC 2544 and 2889 for switches and routers, RFC 3511 and 9411 for firewalls, ITU-T Y.1564 for Ethernet services, TR-398 for Wi-Fi, each cited by section. Cases the standards do not cover, such as failover with your routing table or an upgrade under load, are written from scratch and marked. How long does it take? First draft from 3 business days for one device role, 5 to 10 for a multi-vendor tender with several roles. The review round adds 2 to 3 days depending on the vendor. Can you run it as well? Yes, in CloudLAB, from 2 weeks for a full run, or on your site with a load module that connects out to CloudLAB. The report then comes in the template defined in part 6 of the plan. ## Send the tender text and a network diagram. The scope and the quote come back in a day. First draft from 3 business days. No NetFlow yet is fine: the draft starts from an RFC mix and says so. [Request a plan](https://test4net.com/services/test-plan-design#lead-form) [All services](https://test4net.com/services?hsLang=en) Send the shortlist ## You have the method. Now get the numbers. Name the models and the KPIs that matter. An engineer replies within one business day with a test plan draft and a quote. Prefer to chat? [Message an engineer on WhatsApp](https://wa.me/37491612709) We use what you send only to answer you. See our [Privacy Policy](https://test4net.com/privacy-policy?hsLang=en). [Send the shortlist](https://test4net.com/services/test-plan-design#lead-form) [![TEST4NET LLC](https://test4net.com/hubfs/test4net-logo-fixed.svg)](https://test4net.com?hsLang=en) Independent testing and validation for telecom, information security and cloud infrastructure – real insights, not assumptions [mailto:sales@test4net.com](mailto:sales@test4net.com) #### Navigate - [Home](https://test4net.com/?hsLang=en) - [Why TEST4NET](https://test4net.com/why-test4net?hsLang=en) - [About us](https://test4net.com/about?hsLang=en) - [Contact](https://test4net.com/contacts?hsLang=en) - [Blog](https://test4net.com/blog?hsLang=en) - [Industry News](https://test4net.com/news?hsLang=en) #### Get in touch Sales [sales@test4net.com](mailto:sales@test4net.com) Support [support.test4net.com](https://support.test4net.com) © 2026 TEST4NET LLC. All rights reserved. [Privacy Policy](https://test4net.com/privacy-policy?hsLang=en) [Legal](https://test4net.com/legal?hsLang=en) ```json { "@context" : "https://schema.org", "@id" : "https://test4net.com/#organization", "@type" : "Organization", "address" : { "@type" : "PostalAddress", "addressCountry" : "AM", "addressLocality" : "Yerevan", "postalCode" : "0033", "streetAddress" : "3 Hakob Hakobyan Street (Mergelyan Hub)" }, "alternateName" : "TEST4NET", "contactPoint" : { "@type" : "ContactPoint", "availableLanguage" : [ "en", "ru", "hy" ], "contactType" : "sales", "email" : "sales@test4net.com", "telephone" : "+374-60-88-88-99" }, "description" : "Independent, vendor-neutral lab for testing network and cybersecurity products — NGFW, WAF, IPS, DLP and SASE — and an authorized distributor of test, measurement and network infrastructure solutions.", "email" : "sales@test4net.com", "foundingDate" : "2024", "image" : "https://test4net.com/hubfs/og-t4n.png", "logo" : "https://test4net.com/hubfs/test4net-logo-fixed-2.svg", "name" : "TEST4NET LLC", "sameAs" : [ "https://www.linkedin.com/company/test4net/", "https://t.me/TEST4NET", "https://www.facebook.com/people/Test4net-LLC/61591470856077/" ], "telephone" : "+374-60-88-88-99", "url" : "https://test4net.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://test4net.com/#website", "@type" : "WebSite", "inLanguage" : "en", "name" : "TEST4NET", "potentialAction" : { "@type" : "SearchAction", "query-input" : "required name=search_term_string", "target" : { "@type" : "EntryPoint", "urlTemplate" : "https://test4net.com/hs-search-results?term={search_term_string}" } }, "publisher" : { "@id" : "https://test4net.com/#organization" }, "url" : "https://test4net.com/" } ``` ```json { "@context" : "https://schema.org", "@type" : "Service", "areaServed" : "Worldwide", "description" : "We write the document that decides a tender, an acceptance or your own lab routine: what to test, on which topology and traffic, in what order, and what counts as a pass. Traffic profiles come from your network, pass criteria carry a load level and a duration, every test case names its evidence. The vendor reviews it before the first packet, so the result cannot be argued away afterwards. First draft from 3 business days. You run it in your lab, the vendor runs it in theirs, or we run it in CloudLAB.", "isPartOf" : { "@type" : "WebPage", "url" : "https://test4net.com/services" }, "name" : "Test plan and methodology design", "provider" : { "@type" : "Organization", "name" : "TEST4NET", "url" : "https://test4net.com/" }, "serviceType" : "Test plan and test methodology design for network and security equipment acceptance", "url" : "https://test4net.com/services/test-plan-design" } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://test4net.com/services", "name" : "Services", "position" : 1 }, { "@type" : "ListItem", "item" : "https://test4net.com/services/test-plan-design", "name" : "Test plan and methodology design", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "The tender text or the decision the plan supports, a network diagram, the device list with firmware, a NetFlow export or a pcap sample of a typical week, and your SLA or capacity plan if there is one. Missing items are replaced by stated assumptions in the draft." }, "name" : "What do you need from us to start?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "They are meant to, before the run. One review round with the vendor is included. Every comment is logged with what changed or why it was refused, and the signed version carries that log." }, "name" : "Can the vendor dispute the plan?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes. The plan names the tool class per case: a commercial generator for line-rate and latency cases, TRex or iperf where they are enough, a protocol emulator for routes and tunnels. If a case cannot be run with your tools, the plan says so and offers CloudLAB for that case." }, "name" : "Is it written for the tools we already have?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "RFC 2544 and 2889 for switches and routers, RFC 3511 and 9411 for firewalls, ITU-T Y.1564 for Ethernet services, TR-398 for Wi-Fi, each cited by section. Cases the standards do not cover, such as failover with your routing table or an upgrade under load, are written from scratch and marked." }, "name" : "Which standards does it follow?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "First draft from 3 business days for one device role, 5 to 10 for a multi-vendor tender with several roles. The review round adds 2 to 3 days depending on the vendor." }, "name" : "How long does it take?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes, in CloudLAB, from 2 weeks for a full run, or on your site with a load module that connects out to CloudLAB. The report then comes in the template defined in part 6 of the plan." }, "name" : "Can you run it as well?" } ] } ```