Q. What is Impact analysis? How to perform impact analysis in the project?
A: — Impact analysis means when we are performing regressing testing at that time we are inspecting that the bug fixes are working correctly, and by fixing these bug other components are working fine as per their requirements are they got disturbed.
Q. How to test a web application by manual testing?
A: — Web Testing
During testing the websites the following scenarios should be considered.
Server side interface
Client side compatibility
In the functionality testing of the web sites the following should be tested.
Error message for wrong input
Optional and mandatory fields
Testing will be done on the database integrity.
Testing will be done on the client system side, on the temporary internet files.
Performance testing can be carried out to know the web site’s scalability, or to target the performance in the environment of third party products such as servers and middle ware for potential purchase.
Tested over various Networks like Dial up, ISDN etc
What is the no. of users per time? How many users website can handle at single time.
Check for peak loads & how system behaves.
Large amount of data accessed by user.
Performance of memory, cpu, file handling etc.
Usability testing is the process by which the human-computer communication characteristics of a system are measured, and flaws are identified for correction. Usability can be defined as the degree to which a given piece of software assists the person sitting at the keyboard to accomplish a task, as different to becoming an additional impediment to such success. The broad goal of usable systems is often assessed using several
Ease of learning
Subjective user satisfaction
Server side interface:
In web testing the server side interface should be tested.
This is done by confirm that communication is done properly.
Compatibility of server with software, hardware, network and database should be tested.
The client side compatibility is also tested in various platforms, using various browsers etc.
The main reason for testing the security of an web is to make out potential vulnerabilities and then repair them.
The following types of testing are described in this section:
Performance testing is a rigorous usability estimate of a working system under levelheaded conditions to identify usability troubles and to evaluate measures such as success rate, task time and user satisfaction with requirements. The objective of performance testing is not to find bugs, but to do away with bottlenecks and establish a baseline for future regression testing.
To conduct performance testing is to connect in a carefully controlled process of measurement and analysis. Ideally, the software under test is already established sufficient so that this process can carry on smoothly. A clearly defined set of expectations is necessary for meaningful performance testing.
For example, for a Web application, you need to know at least two things:
expected load in terms of concurrent users or HTTP connections
acceptable response time
Load testing is generally defined as the process of exercising the system under test by feeding it the largest tasks it can operate with. Load testing is sometimes called volume testing, or longevity/endurance testing
Examples of volume testing:
testing a word processor by editing a very large document
testing a printer by sending it a very large job
testing a mail server with thousands of users mailboxes
Examples of longevity/endurance testing:
testing a client-server application by running the client in a loop against the server over an extended period of time
Goals of load testing:
Depiction bugs that do not surface in superficial testing, such as memory management bugs, memory leaks, buffer overflows, etc. Make sure that the application meets the performance baseline established during Performance testing. This is done by running regression tests against the application at a specified maximum load.
Although performance testing and load testing can seen parallel, their objectives are different. On one hand, performance testing uses load testing techniques and tools for measurement and benchmarking reason and uses a variety of load levels whereas load testing operates at a predefined load level, the highest load that the system can accept while still functioning correctly.
Stress testing is a type of testing that is used to find out the constancy of a given system or entity. This is designed to test the software with nonstandard circumstances. Stress testing attempts to find the restrictions at which the system will fail through nonstandard quantity or frequency of inputs.
Stress testing tries to break the system under test by overpowering its resources or by taking resources away from it (in which case it is sometimes called negative testing).
The main idea behind this madness is to make sure that the system fails and recovers benevolently — this quality is known as recoverability.
Stress testing does not break the system but instead it allows monitor how the system reacts to failure. Stress testing observes for the following.
Does it save its state or does it crash suddenly?
Does it just hang and freeze or does it fail gracefully?
Is it able to recover from the last good state on restart?
A Testing to make sure compatibility of an application or Web site with multiple browsers, OS and hardware platforms. Different versions, configurations, display resolutions, and Internet connect speeds all can impact the behavior of the product and introduce costly and embarrassing bugs. We test for compatibility using real test environments.
That is testing how will the system performs in the particular software, hardware or network environment. Compatibility testing can be carry out manually or can be determined by an automated functional. The idea of compatibility testing is to disclose issues related to the product & interaction session test suite.
With other software as well as hardware. The product compatibility is estimated by first identifying the hardware/software/browser components that the product is designed to support. Then a hardware/software/browser matrix is designed that indicates the configurations on which the product will be tested. Then, with input from the client, a testing script is designed that will be sufficient to evaluate compatibility between the product and the hardware/software/browser matrix. Finally, the script is executed against the matrix and any anomalies are investigated to decide exactly where the incompatibility lies.
Some typical compatibility tests include testing your application:
On various client hardware configurations
Using different memory sizes and hard drive space
On various Operating Systems
In different network environments
With different printers and peripherals (i.e. zip drives, USBs, etc.)
62. Which comes first test strategy or test plan?
A:– Test strategy comes first and this is the high level document…. and advance. Testing starts from test strategy and then based on this the test lead set up the
Q. As a testers point of view what is the difference between web based application and client server application ?
A:– According to Tester’s Point of view——
1) Web Base Application (WBA)is a 3 tier application ;Browser, Back end and Server.
Client server Application(CSA) is a 2 tier Application ;Front End ,Back end .
2) In the WBA tester test for the Script error like java script error VB script error etc, that shown at the page. In the CSA tester does not test for any script error.
3) Because in the WBA once changes perform return at every machine so tester has less work for test. Whereas in the CSA every time application need to be install hence ,it maybe possible that some machine has some problem for that Hardware testing as well as software testing is needed.
63. What is the significance of doing Regression testing?
A:– To check for the bug fixes. And this fix should not disturb other functionality
To guarantee the newly added functionality or existing modified functionality or developer fixed bug come up with any new bug or affecting any other side effect. this is called regression test and ensure already PASSED TEST CASES would not arise any new bug.
64. What are the diff ways to check a date field in a website?
A:– There are different ways like :–
1) you can check the field width for minimum and maximum.
2) If that field only take the Numeric Value then check it’ll only take Numeric no other type.
3) If it takes the date or time then check for other.
4) Same way like Numeric you can check it for the Character, Alpha Numeric and all.
6) Check the field for the Null value.
The date field we can check in different ways
Positive testing: first we enter the date in given format
Negative Testing: We enter the date in unacceptable format suppose if we enter date like 30/02/2006 it should show some error message and also we use to check the numeric or text