Saturday, 12 October 2013

System Testing

System testing is the testing of a complete and fully integrated software product.

System testing is nothing but testing the whole application
which was integrated all the modules. The system testing have two types:

1.Fuctionality testing'
2.Non-functionality testing

System testing falls under the black box testing category of software testing.

What do you verify in System Testing ?


-> Testing the fully integrated software and verfiy the how componanet interact with one another and with the system as whole. This is also called End to End testing.

-> Verify thorough testing of every input in the application to check for desired outputs.

-> Testing with hardware and software requirements according to that project  requirements.


End to End Testing:


-> The End to End testing the system from Rewuirement base to delivery base is working peroperly or not.

-> The purpose of end-to-end tests is make ensure that the right information is passed between various system components and systems.

-> End-to-end testing involves ensuring that that integrated components of an application function as expected. The entire application is tested in a real-world scenario such as communicating with the database, network, hardware and other applications.

For example, a simplified end-to-end testing of an email application might involve logging in to the application, getting into the inbox, opening and closing the mail box, composing, forwarding or replying to email, checking in the sent items and logging out of the application.

Type of System Testing :


1.Fuctionality testing'
2.Non-functionality testing

Wednesday, 9 October 2013

Difference between Batch Processing and Interactive Processing


Batch Processing - If we want to run bulk of mainframe files more than one time


The huge volume set of input file running bulk with out user interation. Those input data are saved in Mainframe files and executed by Batch Process.

The jobs are setup made up without any ineractions, The operators specify the below inforamtion correctly in batch job

1) collection of input files
2) And specify the ouput files where we get the output.

While the user submit (SUB) the job, the system Automatically takes the bulk of input data from files and prcessed and saved those result in output file without any manual interaction.



Example :


he way credit card companies process billing is a very good example of batch processing. The credit card owner does not receive a bill for each separate credit card purchase. Instead the bill is created using a batch process and the data are stored there. At the end of the month or the billing cycle, the data are collected as a batch process and the card holder gets the bill for the whole months transaction.




Interactive Processing - Here they ask the input files and ouput files information each an everytime. 


Here user give the input and submit the job and get the ouput files. we get the ouput immediately. Then user specify the some other input and submit the job and get the ouput. So the  input-output-input cycle continue still we get the expected result with user interactions.

This is called Interactive Processing


Example:


An example of an interactive processing system is where an insurance company can make changes to a customer's household insurance, e.g. while the customer is on the phone. The insurance clerk simply calls up details of the customer's policy on the screen, and types in any required changes which immediately update the customer's records. A report of the change would be automatically generated and a copy sent to the customer.

CICS Meaning


This is Transaction Server.

CICS can manage large volumes of transactions. CICS allows transactions to run concurrently at the same time serving many online users.

CICS offers ACID properties. CICS allows sharing of data and resources.

Different CICS services are exposed through a rich set of API(Application programming interface) commands.

To make Cobol program(s) interactive, we code special CICS API commands in the program. CICS programs are not very different from ordinary Cobol programs.


Transaction : 


A transaction is the basic unit-of-work in online systems. A transaction runs one or more  programs to process the data. A user types the input data on the computer screen, and presses Enter to start the transaction. The transaction invokes one or more programs to process the data right away. Immediately, the output results are displayed on the terminal and the transaction ends.

A single business-transaction(such as enrollment of a customer, retirement of an employee) may involve one or more CICS transactions.

Sunday, 6 October 2013

Difference between functional testing and integration testing


Functional Testing :

 

Functional testing is concerned only with the functional requirements of a system or subsystem and covers how well (if at all) the system executes its functions. These include any user commands, data manipulation, searches and business processes, user screens, and integrations.

Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team


Functional testing is when we are testing the software or product as a whole functionality whether it is working properly or not. (Testing button and links)

If you made any changes in any module, we have to verify that whole module is  working as per the functionality or not.

Integration testing :


Integration testing is when you test more than one component and how they functionally working together wiht out any issues. Also verify how the system interacts with your system or the database interacts with your data.

Integration testing tests interfaces between components, interactions to different parts of a system such as an operating system, file system and hardware or interfaces between systems

Test the integrated software only but you test where the data flow is happening and is there any changes happening in the database.

Usually we need fully installed system to perform integration testing. And verify that more componant or module interact each other.

Example:


If we are made changes on Logon page(one module) as per new reqirements. The below testing are

Functinal Testing = verified all the links and buttton on logon page. And give user name and password in logon page and verified its routes to home page successfully or not.

Integration testing = After give user name and password, there is a data flow and also change in database (the login per day increases value by 1).


Remember - clicking links and images is not integration testing. because there is no change in database by just clicking on a link. But while integration testing we are testing data flow (interface between one module to another module)

Types of Integration Testing


1) Top-Down Integration Testing: Top Down Integration as the term suggests, starts always at the top of the program hierarchy and travels towards its branches. This

can be done in either depth-first or breadth-first.

2) Bottom-Up Integration Testing: Bottom –Up integration as it name implies starts at the lowest level in the program structure.

Some Techniques of integration testing: Techniques of integration testing can be given below

1) Top-down testing approach
2) Bottom-up testing approach
3) Big-Bang testing approach
4) Sandwiched testing approach

Conclusion: At last we conclude that Integration testing focuses on testing multiple modules working together.

Whit box testing or glass box testing or structured based technique

We should know what is the processing inside. Its requires knowledge of the language being used inside the application.

Example:

 

Calculator- If we are not get the correct result as per the input, we need to know how those calcluation are don and fix the problem you can find. people dont know anything about the programming cannot do the white box testing.

if we find the issue in blackbox testing, this is not necessary look into the coding. we should performing the white box testing.


Defined by ISTQB


Structure-based testing techniques (which are also dynamic rather than static) use the internal structure of the software to derive test cases. They are commonly called 'white-box' or 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software is implemented, that is, how it works.

 For example, a structural technique may be concerned with exercising loops in the software. Different test cases may be derived to exercise the loop once, twice, and many times. This may be done regardless of the functionality of the software


How to test the white box testing


1) Guarantee that all independent paths within a module have been exercised at least once.
2) Exercise all logical decisions on their true and false sides.
3) Execute all loops at their boundaries and within their operational bounds
4) Exercise internal data structures to assure their validity.

We are using below concept of coverage for structured based technique or white box  testing.


-> code coverage
-> decision coverage
-> statement coverage,
-> structural testing
-> structure-based testing
-> white-box testing

Saturday, 5 October 2013

Black box testing or specification based techninque


As we first understand that we cannot see anything in blackbox. As a same way  we are not know what process happening inside the software.we just verified the output is correct as per the input.

In black box testing we can do the functional testing. we use this concept in Boundary value Analysis technique. you no need to know how the code works. you just need to know how we can give the input and verify the results.

Its applicable for Accepatance testing and System testing.

Example :

Calculator - you enter the some number and check the program gives the correct result. we no need to know about the how the process inside

How to test the black box testing

Black box testing attempts to find errors in the following categories:

Incorrect or missing functions
Interface errors
External database errors
Performance errors
Initialization and termination errors

We used specification based or black box testing for below technique

1) equivalence partitioning;
2) boundary value analysis;
3) decision tables;
4) state transition testing.

 

1) Equalence Partitioning


The idea behind that technique is we can divide the set of test conditions into groups or sets that can be considered as same.

The equalence partitioning technique we need to test only one condition from each partition. This is because all the test condition under the group treat as a same

If one test conditions in a partition works, we can assume all the test condition in the partitions or group will work. Conversely if one of the test conditions in the partitions doesnot work, we can assume that non of the test conditions under group wont work.


Invalid Partition : We can say that set of group or partition as 'INVALID'. Its used for perform the invalid testcases.

Example :

If you are testing for an input box accepting numbers from 1 to 1000 then there is no use in writing thousand test cases for all 1000 valid input numbers plus other test cases for invalid data.

here we need to think 3 views:

Test cases for input box accepting numbers between 1 and 1000 using Equivalence Partitioning:


1) Group or partition the set of testcases for value from 1 to 1000 for all valid inputs. Pick a single value from range 1 to 1000 as a valid test case. If you select other values between 1 and 1000 then result is going to be same. So one test case for valid input data should be sufficient.

2) Group or partition the set of testcases for below 1. I.e. any value below 1, as a invalid input data test case.

3) Group or partition the set of testcases for above 1000. I.e. any value above 1000, as a invalid input data test case.

So using equivalence partitioning you have categorized all possible test cases into three group or partition. Test cases with other values from any class should give you the same result.



2) Boundary Value Analysis (BVA)


For Boundary value Analysis, we can take the minimum and maximum values from the valid partition.


Example :

If you are testing for an input box accepting numbers from 1 to 1000 then there is no use in writing thousand test cases for all 1000 valid input numbers plus other test cases for invalid data.


Test cases for input box accepting numbers between 1 and 1000 using Boundary value analysis:

1) Open Boundary Value = Test cases with test data exactly as the input boundaries of input domain i.e. values 1 and 1000 in our case.

2) Lower open boundary value = Test data with values just below the extreme edges of input domains i.e. values 0 and 999.

3) Higher open boundary value = Test data with values just above the extreme edges of input domain i.e. values 2 and 1001.

Boundary value analysis is often called as a part of stress and negative testing.






Friday, 4 October 2013

CICS table


CICS = Customer Information Control System

CICS maintains the two table

1) PCT - Program Control Table

THe PCT contains the information about the Trans ID and name of the first program to run.

2) PPT - Processing Program Table

The PPT contains the inforamtion about the Program name and load-library address of the program.


While we entered the four digit Trans id into the CICS terminal (Web Browser), its first search the Trans ID in PCT tabel. If its find the Trans ID in PCT, then its search the Program to run in PPT table.

CICS put the Program into disk main storage to run. The Active and running instance are called Task.The output results are displayed on screen and the CICS transaction ends.

Note :

1) We should define the Program in PPT table before we use that Program
2) We should define the Trans Id in PCT tabel before we use the Trans ID.