Testing Component

• Component testing is a method of testing the lowest or the smallest unit of any application.
• Component testing is a sort of white box testing. It looks for bugs and validates the functioning of the modules/programs which are individually testable.
• Project Test Plan - This plan will provide information such as the expected levels of specification and code coverage.
• System Requirements – It is a detailed and structured use case model which can assist in determining the required behaviors for individual domain-level classes sufficiently.
• Component Specifications – In component specification, there are three types of properties should be included from which the functional test cases will be built.
• Component Implementations – Needed information are provided to construct the structural and interaction test case during the actual implementation of the design.
• Desktop computers are personal computers (PCs) designed for use by an individual at a fixed location.
• Servers are computers with high processing speeds that provide one or more services to other frameworks on the network.
• The Macintosh computer was introduced in 1984, and it was the first widely sold personal computer with a graphical user interface.
• Motherboard - It holds and allows communication between many of the crucial electronic components of a system.
• Power Supply - The powerhouse of the computer which guarantees that every component gets the power it needs to function properly.
• Central Processing Unit - The main brain of the computer and the electronic circuitry that execute instructions.
• RAM - Volatile/temporary type of memory
• HDD - A non-volatile computer storage device containing magnetic disks or platters revolving at high speeds.
• Video Card - A dedicated component that hands the images output by your monitor display.
• Optical Drive - Used to read CDs and DVDs, which can be used to listen to music or watch movies.