What is System testing

-
System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.


  • In system testing the behavior of whole system/product is tested as defined by the scope of the development project or product.
  • It may include tests based on risks and/or requirement specifications, business process, use cases, or other high level descriptions of system behavior, interactions with the operating systems, and system resources.

  • System testing is most often the final test to verify that the system to be delivered meets the specification and its purpose.

  • System testing is carried out by specialists testers or independent testers.

  • System testing should investigate both functional and non-functional requirements of the testing.

Types of System Testing


  • Usability Testing -  Usability testing mainly focuses on the user's ease to use the application, flexibility in handling controls and ability of the system to meet its objectives

  • Load Testing - Load testing is necessary to know that a software solution will perform under real life loads.

  • Regression Testing - Regression testing involves testing done to make sure none of the changes made over the course of the development process have caused new bugs. It also makes sure no old bugs appear from the addition of new software modules over time.

  • Recovery Testing - Recovery testing is done to demonstrate a software solution is reliable, trustworthy and can successfully recoup from possible crashes.

  • Migration Testing - Migration testing is done to ensure that the software can be moved from older system infrastructures to current system infrastructures without any issues.

  • Functional Testing - Also known as functional completeness testing, functional testing involves trying to think of any possible missing functions. Testers might make a list of additional functionalities that a product could have to improve it during functional testing.

  • Hardware/Software Testing - IBM refers to Hardware/Software testing as "HW/SW Testing". This is when the tester focuses his/her attention on the interactions between the hardware and software during system testing.

Comments

Post a Comment

Popular posts from this blog

Compare a range of Hardware and Software Troubleshooting Tools

-
Image
H ARDWARE TESTING TOOLS  Hardware testing tools are usually for testing a computer while it off, and to diagnose/fix more complex hardware problems. These tools I am about to compare all have different uses and so are hard to compare in this format MULTI-METER  A multi-meter is used to measure the electrical properties flowing through a cable, such as amperage, voltage and electrical resistance. It can measure other electrical variables as well, but these are mostly not used for computer maintenance purposes.  The multi-meter is generally just used to narrow down the problem to the power supply. However it can also be used to check if the power source the computer’s power supply is connected to, is also running within tolerances. ETHERNET CABLE TESTER  An ethernet cable tester is used to test an ethernet cable’s ability to send/receive data. The tester will usually send some test data or power to the other end, which the tester then checks to see if it rec
Read more

What is Boundary value analysis in software testing?

-
Image
Boundary value analysis  is based on testing at the boundaries between partitions. Here we have both valid boundaries (in the valid partitions) and invalid boundaries (in the invalid partitions). As an example, consider a printer that has an input option of the number of copies to be made, from 1 to 99. To apply boundary value analysis, we will take the minimum and maximum (boundary) values from the valid partition (1 and 99 in this case) together with the first or last value respectively in each of the invalid partitions adjacent to the valid partition (0 and 100 in this case). In this example we would have three equivalence partitioning tests (one from each of the three partitions) and four boundary value tests.  While testing why it is important to do both equivalence partitioning and boundary value analysis? because every boundary is in some partition, if you did only boundary value analysis you would also have tested every equivalence partition. However, this approach may
Read more