Movatterモバイル変換


[0]ホーム

URL:


Skip links

Try QA

Main navigation

Study material for ISTQB Exam Certification Foundation level, Premium & Free for ISTQB and ASTQB Exam, Certification questions, answers, software testing tutorials and more

What is Dynamic testing technique? Examples, Types, Advantages & Disadvantages

Dynamic testing technique is the type of testing that validates the functionality of an application when thecode is executed / by executing the code. In simple terms dynamic testing is performed by actually using the application and seeing if a functionality works the way it is expected to. There is also something called ‘static’ testing. Learning about static testing helps understand dynamic testing better, so let’s summarize static testing first.

Table Of Contents

What is Static Testing?

Static testing as the name itself suggests is static in nature, which also means there are no changing conditions or parameters. In other words, this is performedwithout executing the code.

For example, when you are verifying a document or testing a document, you will go through the document, review it and then suggest or make changes.

Also, when there is a code review /walkthrough, the development team goes over the code step by step and checks whether the code written is according to the development standards and also it traverses through correctly to achieve the results desired.

Since, we are not changing anything in the documents, but also reviewing them, it is called static testing. We are testing, but it is static in nature.

Other examples for static testing are review oftest strategy document,test plan document, test case walkthrough, Inspection of the code etc.What Is Dynamic Testing Technique - Examples, types advantages

What is Dynamic Testing?

Now, let’s look at Dynamic testing. The name itself suggests that it is “Dynamic” in nature, which means changing. This is the kind of testing that we do with changing values or conditionsby executing the code.

This involves testing the application in real-time by giving inputs and examining the result or the output value of behavior.

Dynamic Testing Example

The easiest example to understand this is the login functionality of any application, like Google’s gmail.com. If we are creating an account, and a password for the account, you would have certain rules for creating a strong password.

For instance, 8 characters long, needs to have a capital letter and at least one special character.

These are nothing but different conditions or parameters and if the user inputs any value that deviate from these rules, the application should either warn or reject.

If you are testing this functionality as an example, you would input all the conditions required to test this and then validate the output.

You would also input the non-working parameters, for example, input a 4-character password and verify if there is an error that is thrown. This is all part of Dynamic testing.

Types of Dynamic TestingDynamic Testing Types Examples

Dynamic testing is broadly classified into two types.

  • Whitebox testing – Whitebox testing looks at the internal workings of the code. For this type of testing, the tester should know the code development, review and be able to interpret the code.
  • Blackbox testing – Blackbox testing looks at only the functionality of the Application Under Test (AUT). This does not require the tester to know the implementation details or be able to interpret the inner workings of the code. This is the type of testing mostly done by the QA department.

Since we are interested more in learning about Blackbox testing, we also need to know that there are again two broad types of Blackbox testing.

  • Functional Testing – As the name itself suggests, this is the type of testing that validates the functionality of the application.
  • Non-Functional Testing – Non-Functional testing covers the aspects of performance, recovery, compatibility testing etc. These are non-functional in nature. And there may be a separate division in the organizations to do the non-functional testing.

Dynamic testing is performed at different levels. Let’s look at the basic definition of what each testing means.

  1. Unit testing – Simply put, the testing done by the developers right after they build the code to ensure their code is working as they expected and according to the requirements.
  2. System testing – This is the type of testing the QA department does after the code has been built and this covers the entire system/application in terms of testing. The QA team does thorough testing to make sure the functionality of the system is in-line with the requirements.
  3. Integration testing – This is a joint effort (in most companies) by the QA and development teams to make sure each individual module (after being tested) then connected to other modules or systems is still working as expected. This is basically the testing for the entire workflow from start to end.
  4. User Acceptance Testing (UAT) – This is done by the UAT team (User Acceptance Testing) with the aid of QA team. The business users write their own test cases and perform testing more geared towards the user’s perspective unlike what the QA does, more toward system’s perspective.

There are advantages to using dynamic testing. At the same time there are some disadvantages. Let’s look at the advantages first.

Advantages of Dynamic Testing

  • Dynamic testing is thorough, which looks at in-depth functionality of the application so the quality is of highest standards.
  • Dynamic testing process is well-established and hence the application is tested from user’s and business perspective thus increasing the quality standards.
  • Complex defects can be caught which may have escaped the review processes
  • Dynamic testing can be automated using tools

Disadvantages of Dynamic Testing

  • Since Dynamic testing follows a complex detailed process, it takes time.
  • It is time consuming and it costs more money to the organizations because of the need for the resources and time.
  • Dynamic testing is usually performed after coding is completed and hence defects are discovered later in the lifecycle

In a nutshell, Dynamic testing technique is the type that is followed in all the organizations today. It is used as a tool that the QA can rely on and has successfully shown results of higher quality when followed properly in organizations. This is extremely useful technique in software testing.

Other popular articles:

Reader Interactions

Comments

  1. To be more Clear, Static Testing comes under verification whereas Dynamic Testing comes under Validation.

  2. Guys you are confusing me…a clear distinction please?

  3. no, during verification process, only static testing techniques are applied.

  4. “It is done during Validation process.” – not only validation, during verification as well.

Leave a ReplyCancel reply

Your email address will not be published.Required fields are marked*

Primary Sidebar

Search

  

ISTQB Certification Exam Study Material

Chapter 1. Fundamentals of testing
What is Software testing?
Whyis testing necessary?
Software testing objectives and purpose
Whatis Defect or bugs or faults?
Whatis a Failure?
Fromwhere do Defects and failures arise?
Whendo defects arise?
Whatis the cost of defects?
Defector Bug Life Cycle
What is the difference between Severity and Priority?
Principlesof testing
Fundamentaltest process
Psychologyof testing
Independenttesting- it’s benefits and risks
SoftwareQuality
Chapter 2. Testing throughout the testing lifecycle
Whatis Verification?
Whatis Validation?
CapabilityMaturity Model (CMM-Levels)
SoftwareDevelopment Life Cycle
SoftwareDevelopment Life Cycle (SDLC) phases
SoftwareDevelopment Models
Waterfallmodel
V-model
Incrementalmodel
RADmodel
Agilemodel
Iterativemodel
Spiralmodel
PrototypeModel
SoftwareTesting Levels
Unittesting
Componenttesting
Integrationtesting
BigBang integration testing
Incrementaltesting
Componentintegration testing
Systemintegration testing
Systemtesting
Acceptancetesting
Alphatesting
Betatesting
SoftwareTest Types
Functionaltesting
Non functionaltesting
Functionalitytesting
Reliabilitytesting
Usabilitytesting
Efficiencytesting
Maintainabilitytesting
Portabilitytesting
Baselinetesting
Compliancetesting
Documentationtesting
Endurancetesting
Loadtesting
Performancetesting
Compatibilitytesting
Securitytesting
Scalabilitytesting
Volumetesting
Stresstesting
Differencebetween Volume, Load and stress testing in software
Recoverytesting
Internationalizationtesting and Localization testing
Confirmationtesting
Regressiontesting
Structuraltesting
MaintenanceTesting
Impactanalysis
Chapter 3. Static Techniques
Testdesign techniques
Statictest technique
Whatis static Testing?
Usesof Static Testing
Informalreviews
Formalreviews
Theroles and responsibilities of the moderator, author, scribe, reviewers and managers involved during a review
Typesof review
Walkthrough
Technicalreview
Inspection
Whatis static analysis?
Whatis a static analysis tools?
Chapter 4. Test design techniques
Testanalysis
Traceability
Testdesign
Testimplementation
Testdesign technique
Categoriesof test design techniques
Static testing techniques
Dynamictesting technique
i.Black box testing or Specification-based
Equivalencepartitioning (EP)
Boundary Value Analysis (BVA)
whyit is important to do both EP and BVA
Decisiontables
Statetransition testing
Usecase testing
ii.White box testing or Structure-based
iii.Experience-based testing
Errorguessing
Exploratorytesting
Structurebased technique
Testcoverage
Whereto apply this test coverage?
Whyto measure code coverage?
Howwe can measure the coverage?
Typesof coverage
Statementcoverage
Branch Coverage or DecisionCoverage
Conditioncoverage
Howto choose that which technique is best?
Chapter 5. Test management
Rolesand responsibilities of a Test Leader
Rolesand responsibilities of a Tester
Purposeand importance of test plans
Thingsto keep in mind while planning tests
Whattesting will involve and what it will cost?
Estimationtechniques
Factorsaffecting test effort
Test strategy
Testmonitoring
Testcontrol
Configurationmanagement
Risksin software testing
Productrisk
Projectrisk
Risk-basedtesting
Riskanalysis
Incidentmanagement
Incidentlogging Or How to log an Incident
Whatare incident reports?
Howto write a good incident report?
Whatis test status report?
Chapter 6. Tool support for testing
Typesof test tools
Toolfor management of testing and tests
Testmanagement tools
Requirementsmanagement tools
Incidentmanagement tools
Configurationmanagement tools
Statictesting tools
Reviewprocess support tools
Staticanalysis tools (D)
Modellingtools (D)
Testspecification tools
Testdesign tools
Testdata preparation tools
Testexecution and logging tools
Testexecution tools
Testharness/ Unit test framework tools (D)
Testcomparators
Coveragemeasurement tools (D)
Securitytools
Performanceand monitoring tools
Dynamicanalysis tools (D)
Performancetesting, Load testing and stress-testing tools
Monitoringtools
Advantagesand benefits of using testing tools
Disadvantagesand risks of testing tools
Factorsfor software testing tool selection
Proof-of-conceptor piloting phase for tool evaluation

Secondary Sidebar

Popular Posts

Trending Posts

Categories

All content is copyright of tryqa.com, tryqa.com was earlier called ISTQBExamCertification.com

[8]ページ先頭

©2009-2025 Movatter.jp