Categories
Manual Testing Software Testing

Web based application | Types of Applications | Advantages and Disadvantages

What is web based System or Application?

Any application which can be accessed through the URL is called web based application.

In the web-based application entire software is installed at the server. Users access the application from a browser using URL.

Architecture / Functions of web based application :

Web based application consists of Web server, Application server and Database server.

Web server contains all the pages like images, static HTMl files, JS etc

Application server contains the entire business logic written in Programs like Java and has been uploaded in jars, ears, wars etc.

Database server Contains entire data stored in the form of tables.

Advantages of Web based applications:

  1. Faster in access if the bandwidth is high
  2. security from data hacking and virus
  3. maintenance is easy
  4. Multiple users can access the a[application
  5. No installation is required
  6. end users resources are not utilize

Disadvantages of Web based applications :

  1. If the server goes down no one can access the application.

 

 

 

Categories
Manual Testing Software Testing Uncategorized

Client Server Application | Types of Applications | Advantages and Disadvantages

 

In Client Server application, unlike Standalone Application, part of application is installed on to the client system and the remaining part is installed on to the server machine.

Architecture:

Client Server Applications

Both Client and server interact with the help of network/internet.

Advantages:

  • Easy to access and faster in access if the bandwidth is more
  • Data security from data hacking and virus
  • Data sharing is possible
  • Maintenance is not so tough
  • Multiple users can access the application.

Disadvantages:

  • Installation is still required at client’s place
  • End users resources are utilized low
  • If the server goes down no one can access the application
Categories
Manual Testing Software Testing

Types of Applications| Stand Alone Application

Applications are of three types:

  1. Stand alone application
  2. Client server application
  3. Web based application

1. Stand alone application:

software installed in one computer and used by only one person.

For ex – Installing s/w of a Calculator, Adobe Photoshop, MS Office, AutoCad

Advantages:

  • Faster in access.
  • Secured from Data hacking and virus.

Disadvantages:

  • Single user access at a time.
  • Installation is required.
  • End user system resources utilized.
  • No data sharing
  • Maintenance is tough with respect to both user and company

Architecture:

In the stand alone application architecture there is no question of any servers and entire application is installed a he end user machine.

This is about Stand alone application.

Next about Client Server Applications

Categories
Manual Testing Software Testing

System Testing

Once Integration testing is over we go for system testing.

System Testing:

Checking the end to end flow of the application is know as System Testing.

What is end to end flow?

Navigating through all the modules of an application is known as end to end flow.

In system testing we are going to navigate through all the modules and check the system as a whole.

Note:

1. In System testing testing environment is similar to production environment.

2. During system testing we need to wait for certain transactions to complete.

Example:

If we take gmail application the following are the scenarios for system testing.

1. Login to the application, check the inbox and logout.

2. Login to the gmail application, compose a mail and logout.

3. Login to the application, goto spam, delete all spam messages and logout.

These are some of the scenarios for gmail application for system testing.

Let us see about parts of an application in the next post…

Thank u…

 

 

Categories
Manual Testing Software Testing

Types of Integration Testing in Software Testing

Once functional testing is over we are going to perform Integration Testing.

Integration Testing:

Checking the data flow between the modules or interfaces is known as Integration testing.

In Integration testing we check if the data created in one module is reflected or transferred or shown in other respective modules.

Example:

If we take gmail application we can write the following scenarios for Integration testing:

1. If we login to the gmail with our login credentials the username should be displayed on the home page. Here the data ie., username is carried from login page to the home page.

2. If we create a mail in compose and click on send, the mail should be present in the Sent items.

3. If we create and mail and close the mail, the mail should be saved as draft and should be present in the drafts.

These are some of the examples of integration testing scenarios on gmail application.

Types of Integration testing:

There are two types of integration testing:

1. Incremental Integration Testing

2. Non Incremental Integration Testing

1. Incremental Integration testing:

Whenever there is clear relationship between modules then we go for Incremental Integration Testing.

Incremental Integration testing is of two types:

a) Top down Incremental Integration Testing

b) Bottom up Incremental Integration Testing

a) Top down Incremental Integration Testing:

In this type of testing we are going to add the modules one by one from top to bottom and check the data flow in the same order.

b) Bottom up Incremental Integration Testing:

In this type of testing we are going to add the modules one by one from bottom to up and check the data flow in the same order.

2. Non Incremental Integration Testing:

We go for this testing whenever we don’t have clear relationship between the modules. This type of testing is also known as Big Bang method.In these cases we create the data in one module and bang on all other modules and check for the data flow. Hence it is known as Big Bang Method.

Note: Sandwich Testing is the combination of incremental and non incremental testing.

Let us see about System testing in the next post..

Thank u….

Categories
Manual Testing Software Testing

Functional Testing

Functional Testing:

Checking each and every component of a module or modules of an application independently is known as Functional Testing.

Terms used in functional Testing:

  • Maximum Test coverage: If testing is done for all positive and negative values the we say maximum test coverage ha been achieved.
  • Positive Testing: Testing for  positive values or we can say testing the component with valid data is called Positive Testing.
  • Negative Testing: Testing for negative values or we can say testing the component with invalid data is called Negative Testing.
  • Over Testing: Testing similar type of values repeatedly is known as Over Testing.

Process for Functional Testing:

  • During functional testing always start with positive testing.
  • Once the positive testing is done continue with negative testing.
  • Do not perform over testing.
  • We should not make any assumptions, get them clear from the concerned person.
  • We stop testing when ever we feel that maximum test coverage is achieved ie., all positive and negative values are covered.

Note:

While testing one component the other components should be entered with positive values only.

Let us see abut Integration testing and it’s types in the next post….

Thank u……

 

Categories
Manual Testing Software Testing

Black Box Testing

Black Box Testing:

Black Box testing is done by the Test Engineers in which they are going to check functionality of the application according to the customer requirements.

In simple words it can be called as Testing.

Other definitions for testing are:

  • Checking the application with intention of finding defects or bugs in the application is known as Testing.
  • The process of testing application till it is stable or bug free or works according to requirements is known as Testing.

Types of Black box testing:

  1. Functional Testing
  2. Integration Testing
  3. System Testing

1. Functional Testing:

Checking each and every component of a module or modules of an application independently is known as Functional testing.

2. Integration Testing:

  • Checking the data flow between the modules or the interface between the modules is known as Integration Testing.
  • In Integration Testing we check if the data created in one module is reflected or transferred or shown in other respective modules.

3. System Testing:

  • Checking the end to end flow of an application is called System Testing.
  • In this we navigate through all the modules of an application and check the system as a whole.

These are the types of Black box testing.

Let us see about each type in detail in future posts.

Thank u…..

 

 

Categories
Manual Testing Software Testing

White Box Testing Types

Types of White Box testing:

  1. Path Testing
  2. Conditional Testing
  3. Loop Testing
  4. Memory Testing
  5. Response Time

1. Path Testing:

  • It is done to know the flow of execution of the program.
  • It is also done to know the total number of paths.

2. Conditional Testing:

  • Here developers check if the written program is executed for both true and also false conditions.

3. Loop Testing:

  • Here developer checks if the written program is executed successfully for all the number of loops written in the program.
  • If the condition is satisfied in between then the program should stop and come out of the loop else it should execute for complete number of loops and then stop execution.

4. Memory Testing:

  • here developers identify the unused lines of code ie., unused variables and unused functions and remove them which ever is not required.
  • This is done with the help of some tools like Rational Purifier.

5. Response Time:

  • Here developer checks the execution time of the program with the help of some tools like Rational Quantifier.

These are the types of White Box Testing.

Let us see the black Box Testing in the next post….

Thank U……

 

 

 

 

 

Categories
Manual Testing Software Testing

Models of SDLC : Hybrid Model

Hybrid Model:

  1. Hybrid model is the combination of two Models.
  2. Generally we go for Hybrid model when ever we want the characteristics of two models together.

Examples of Hybrid model is combination of Spiral and Prototype Models.

Process:

  • First we are going to collect the requirements of one Module.
  • Develop the prototype.
  • Test the prototype
  • Customer review.
  • Customer approval
  • Then design of that prototype for that module.
  • After design, coding and then testing.
  • Deploy to the customer.
  • This process continues for all the modules present in the application.

In the next post we are going to discuss types of testing

Thank u….

 

 

Categories
Manual Testing Software Testing

White Box Testing in Software Engineering | Explained

As discussed in previous post Types Of Testing, there are 3 types of software testing and White Box testing is one of them. Now we will take a look closer on the white box testing.

White Box Testing

This type of testing is done by the Developers, once the coding is completed. In this they are going to check each and every line of code.

If developers do the white box testing manually several problems may arise.

  •  No accuracy will be maintained.
  • Tedious process.
  • Time consuming.

So developers never do white box testing manually. They write some unit test programs with the help of some tools like JUnit etc...

The main aim of unit test program to check every program written by the developer will work properly and gives desired output.

There are many Advantages of  writing unit test program with the help of tools. some of them  are

  1. Time saving since they can be executed in less time.
  2. Accuracy is maintained since tools do not skip testing any of the main program.
  3. Unit test programs can be reused when ever bug fixes are done by the developers.

By doing White box testing developers can reduce some amount of bugs before handing over the application to the test engineers.

This is the high level process of White box testing.

In White Box Testing, we have different types of Testing available. To Know more read the post about  White box Testing types