Virtual Testing©

	Virtual Testing Networks' Testing: Any running network regardless of business types may have 10,000 to over 100,000 items running. These items locally and remotely interface, communicate and exchange data and messages plus the entire network must be secured. These running items on such networks are infrastructure, software system, security system, vendors software, Legacy system, supporting software, ..etc. The question is:        How do we test such a network? The current existing testing is done independent or in coordination by each department or even business units which leave gabs or gates for hackers and issues. Performance issues can also be added to these independently running components. Virtualization, DevOps, DataOps and Machine Learning are taking networks into a new level and it is becoming difficult to run such independent testing. Testing in a vacuum is costly since hackers attacked every networks running items include the internet itself. What is Virtual Testing? Virtualization as a tool or an approach is not fully understood by IT community, nor implemented properly. Virtual Testing does not have a clear definition. Our attempt is to harness the power of virtualization into virtual tools to perform testing with dynamic intelligent integrated automated components which we call them Virtual Testing Containers. For example, if we have three teachers Math, English and Science and we asked them to edit a number of documents. The three teachers can work together on one computer editing the same documents, or we can create three separate folders each folder has a copy of all the documents on each teacher's own computer. In short, we created three virtual folders for each teacher to work independently with each teacher's own speed and knowledge base without interruption. We are presenting virtualization as a tool to create a Virtual Container which would contains the entire (Vertical Scaling) target system (components) to be tested. We are also free to create any number of the same container (Horizontal scaling) with the target system (components). The only overhead of Virtual Testing Container is creating a virtual server which would be our Virtual Testing Container. DevOps and DataOps are the center of all these virtual creations. Our Virtual Testing Approach: Our goal is to build a virtual testing system which is the following:        1. Containers and Components        2. Secured        3. Intelligent        4. Independent        5. Automated        6. Integrated        7. Customized        8. Scalable (Vertically and Horizontally)        9. Machine Learning background support The IT community needs to start thinking in term of Virtual Containers and Virtual Components the same way the IT community views folders and files. For example, the difference between Monolithic and Microservices architecture is that Monolithic is a big chunk of a system and Microservices is small pieces of independent modules. Our answer is: It does not matter which architect is running since it will be encapsulated within a Virtual Container as an independent Virtual component(s) with all its support software. IT needs to think of Virtual Container is a big folder which may contain other folders and files. Virtual Components would be folders and files within the Virtual Container folder. We view Microservices, Macro services, web services, API, third party software, Legacy System, ..etc as a service. Such a service can be hosted with a virtual container to run independently. Vertical and Horizontal Scaling: Vertical means that any number of Virtual Components can added the Virtual Containers. Horizontal means we are free to create any number of Virtual Container as long as our system memory allows. Coming Soon