Skip to main content

3.11A System Testing

3.11A System Testing


Following are some of the important testing for SDLC:

Unit Testing


  • Unit tests include tests of each separate program or module.


  • Testing is generally conducted by developers themselves. It is conducted as and when a program or module is ready and it does not require to wait until completion of the total system.


  • Unit testing is done through a white box approach wherein internal program logics are tested.


Integrated Testing


  • Integrated test includes integration or connection between two or more system components.


  • Purpose of the integration test is to validate accurate and correct information flow between the systems.


System Testing


  • System testing tests the complete and full system capabilities.


  • It covers end to end system specifications.


  • It covers functionality test, recoverability test, security test, load test, volume test, stress test and performance test.


Final Acceptance Testing


  • Final acceptance test consists of two tests i.e. QAT (quality assurance test) and UAT (user acceptance test)


Regression Testing


  • Meaning of regression is to return to an earlier stage.


  • Objective of a regression test is to confirm that a recent change has not introduced any new faults and other existing features are working correctly.


  • It must be ensured that the same data (which was used in earlier tests) should be used for the regression test. This will help to confirm that there are no new errors or malfunctioning.


Sociability Testing


  • Sociability means the quality of being able to merge with others.


  • Objective of the sociability test is to ensure that the new system works as expected in existing infrastructure without any adverse impact on other existing systems. the application works as expected in the specified environment where other applications run concurrently.


Pilot Testing


  • A pilot test is a small-scale preliminary study to understand and evaluate system functionality and other aspects.


  • Pilot test is conducted for only few units or few locations to evaluate the feasibility.


  • Objective of the pilot test is to determine the feasibility of the new system before full fledged implementation.


Parallel Testing


  • Parallel test involves the testing of a new system and comparing the results of a new system with that of an old system.


  • Objective of parallel testing is to ensure that the new system meets the requirements of the user.


White Box & Black Box Testing

White Box Testing


  • In white box testing, program logic is verified.


  • For conduct of white box testing, appropriate knowledge of programming language is a must.


  • White box testing is generally conducted for unit testing


Black Box Testing


  • In black box testing, emphasis is on functionality of the system.


  • For conduct of black box testing, knowledge of programming language is not mandatory.


  • Black box testing is generally conducted for user acceptance test and interface testing.


Alpha & Beta Testing


Alpha Testing


  • Alpha testing is conducted by internal user


  • Alpha test is conducted before beta test


  • Alpha test may or may not include full functionality test



Beta Testing


  • Beta test is conducted by external user


  • Beta test is conducted after alpha test


  • Beta test is generally conducted for full functionality


Key aspects from CRISC exam perspective


Below table covers important aspect from CRISC exam perspective:



CRISC Questions 

Possible Answer 

In which test, testing of architectural design is conducted?

Integration testing

In which test, testing for linked and connected modules is conducted?

Integration Testing

Failure of which test has the greatest impact?

Acceptance Testing

Which test is required to determine the ability of a new system to operate in the existing environment without any adverse impact on other systems?

Sociability Testing



Self-Assessment Questions


Practice Questions - 3.11A System Testing

Popular posts from this blog

1.1 Risk Capacity, Risk Appetite and Risk Tolerance

1.1   Risk Capacity, Appetite and Tolerance First step of any risk management learning is to understand following three important terms: Risk Capacity Risk Tolerance  Risk Appetite  Let us understand the difference between Risk Capacity, Risk Appetite and Risk Tolerance:   Parameter Descriptions Risk Capacity Maximum risk an organization can afford to take. Risk Tolerance Risk tolerance levels are acceptable deviations from risk appetite. They are always lower than risk capacity. Risk Appetite Amount of risk an organization is willing to take.   Let us understand this with an practical example: Mr. A’s total saving is $1000. He wants to invest in equities to earn some income. Being risk conscious, he decides to invest only up to $700.  If the markets are good he is willing to further invest  $50.  Risk Capacity: Total amount available i.e. $1000 RIsk Appetite: His willingness to take risk i.e. $700 Risk Tolerance: A...
Read more

Welcome to first ever Web Book on CRISC (Certified Risk & Information System Control)

We welcome you to access this web book on CRISC (Certified Risk & Information System Control) by ISACA.   Features of this web book are as follow:  This web book is designed on the basis of official resources of ISACA.  Web book is designed specifically for candidates from non-technical background. Topics are arranged segment wise and aligned with latest CRISC Review Manual.  500 + Exam oriented practice questions.  Start your preparation here: Chapter 1   Chapter 2   Chapter 3   Chapter 4   CRISC - Recorded Lectures  We are happy to announce that CRISC lectures is now made available in Udemy in recorded form. You can access them at any time as per your convenience. You will have life time access for the recorded lectures.  Following are the salient features of the lecture: This course is designed on the basis of official resources of ISACA. Course is designed specifically for candidates from non-technical backgrou...
Read more

2.7 Risk Analysis Methodologies

2.7 Risk Analysis Methodologies Risk analysis is the process of ranking of various risk so that areas of high can be prioritized for treating them.   Risk can be measured and ranked by use of any of the following methods:   Quantitative Risk Assessment Qualitative Risk Assessment Semi-quantitative Risk Assessment   Factor that influence the selection for above technique is availability of accurate data for risk assessment. When data source is accurate and reliable, organization will prefer quantitative risk assessment as it will give risk value in some numeric terms like monitory values. Monetary value is easy to evaluate to determine the risk response. Quantitative Risk Assessment In quantitative risk assessment, risk is measured on the basis on numerical values. This helps in cost benefit analysis as risk in monetary term can be easily compared to cost of various risk responses.   In quantitative risk assessment, various statist...
Read more