UseCase :
It is indepth detailed description about Customer
Requirments. it is developed from BRS/SRS. it is prepared
by business analyst or QA Lead.
Testcase:
It is a doument describing the input,action and
expected response to determine wether the application is
working correctly according to the customer requirments.
it is derived from srs,usecases and test scenarios. while
developing test cases we can find gaps in the requirments
also.
Use case is a set of scenario's of User requirement.
Test Case is a document Designed based on the Use case
To Evaluate between Expected & Actual Result.
USE cases is a pictorial representation of requirments.
Test Case is a document Designed based on the Use case
To Evaluate between Expected & Actual Result.
Wednesday, July 28, 2010
Tuesday, July 27, 2010
Difference between User Acceptance Test cases and System Test Cases
System Testing:
Finding the defects when the system is tested as a whole this also called as end to end testing. In this testing tester needs to test the application from log-in to log-out.
User Acceptance Testing:
User acceptance testing is to get the acceptance from the client. UAT is generally done at client's environment. Before UAT pre UAT should be done.
Finding the defects when the system is tested as a whole this also called as end to end testing. In this testing tester needs to test the application from log-in to log-out.
User Acceptance Testing:
User acceptance testing is to get the acceptance from the client. UAT is generally done at client's environment. Before UAT pre UAT should be done.
Labels:
System testing,
User Acceptance Testing
Web Testing Interview Questions
1. Describe some of the possible web page futures.
2. Question: What are possible configurations that could affect the testing strategy of any web site?
Answer: Hardware platform (PC, Mac), Browser software and version, Browser Plug-Ins, Browser settings options, Video resolution and Color Depth, text size
3. What is website usability testing.
Ans:- Usability testing is a technique used to evaluate a product by testing it on users…Testing to check “User Friendliness”
4. Why spell checker is not enough during testing spelling on web page?
Ans:- Because there are Pictures/Logos/Photos that may contain wrong spellings and the spell checker is not able to identify those errors.
5. Question: Name a few website mistakes that could cause configuration and compatibility bugs.
Answer: Non standard colors, frames, tables etc.
6. Question: What the latest web technologies do you know?
Answer: RSS
7.Question: Name some Alternative Browsers.
Answer: Opera, Mozilla
8. Describe some Caching Issues.
:-Cache is
A) HTML meta tags to prevent page caching. Every single possible combination and none work.
B) PHP Headers to prevent page caching. Every single possible combination and none work.
C)Proxy server caching issues.
NOTE:-So its slow down the overall Performance of the system. So we used to clean up the old cache time by time.
9. What HTML standard?
10.What web specific types of testing?
11.What is static and what is dynamic web page?
12.Question: Can the Netscape scripting host without plug-ins run Microsofts JScript on the client side?
Answer: No
13. Question: What is Glyphs?
Answer: Glyph is the picture of the character.
14.What techniques will cause double-byte problems to show up?
Ans:- ColdFusion MX is not compatible for unixs(Solaris).
15. What is Alt Key Input?
16. How will you decide when and what to test during performance testing?
17. Question: What types of web testing security problems do you know?
Answer:(Denial of Service (DoS) attack, buffer overflow)
18. Question: What types HTTP Response Codes do you know?
Answer: ( 2xx – success, 3xx – Redirection, 4xx – Client Error, 5xx – Server Error)
19. What errors can occur when the page loads?
20. What are the metrics what can be used during performance testing?
21. What HTML file extension can be used?
22. What are the differences between testing WEB application and testing client-sever
application?
23. Write test cases for Search Engine?
24. Difference between HTTP and HTTPS? Explain how the data is secured in
HTTPS?
25. What does DNS contains?
26. What is the difference between authentication and authorization?
27. What type of security testing you performed?
28. Difference between GUI and Usability Testing
2. Question: What are possible configurations that could affect the testing strategy of any web site?
Answer: Hardware platform (PC, Mac), Browser software and version, Browser Plug-Ins, Browser settings options, Video resolution and Color Depth, text size
3. What is website usability testing.
Ans:- Usability testing is a technique used to evaluate a product by testing it on users…Testing to check “User Friendliness”
4. Why spell checker is not enough during testing spelling on web page?
Ans:- Because there are Pictures/Logos/Photos that may contain wrong spellings and the spell checker is not able to identify those errors.
5. Question: Name a few website mistakes that could cause configuration and compatibility bugs.
Answer: Non standard colors, frames, tables etc.
6. Question: What the latest web technologies do you know?
Answer: RSS
7.Question: Name some Alternative Browsers.
Answer: Opera, Mozilla
8. Describe some Caching Issues.
:-Cache is
A) HTML meta tags to prevent page caching. Every single possible combination and none work.
B) PHP Headers to prevent page caching. Every single possible combination and none work.
C)Proxy server caching issues.
NOTE:-So its slow down the overall Performance of the system. So we used to clean up the old cache time by time.
9. What HTML standard?
10.What web specific types of testing?
11.What is static and what is dynamic web page?
12.Question: Can the Netscape scripting host without plug-ins run Microsofts JScript on the client side?
Answer: No
13. Question: What is Glyphs?
Answer: Glyph is the picture of the character.
14.What techniques will cause double-byte problems to show up?
Ans:- ColdFusion MX is not compatible for unixs(Solaris).
15. What is Alt Key Input?
16. How will you decide when and what to test during performance testing?
17. Question: What types of web testing security problems do you know?
Answer:(Denial of Service (DoS) attack, buffer overflow)
18. Question: What types HTTP Response Codes do you know?
Answer: ( 2xx – success, 3xx – Redirection, 4xx – Client Error, 5xx – Server Error)
19. What errors can occur when the page loads?
20. What are the metrics what can be used during performance testing?
21. What HTML file extension can be used?
22. What are the differences between testing WEB application and testing client-sever
application?
23. Write test cases for Search Engine?
24. Difference between HTTP and HTTPS? Explain how the data is secured in
HTTPS?
25. What does DNS contains?
26. What is the difference between authentication and authorization?
27. What type of security testing you performed?
28. Difference between GUI and Usability Testing
Labels:
Web testing,
Website testing
What is difference between client server and Web Testing?
In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, backend. This environment is mostly used in Intranet networks. You are aware of number of clients and servers and their locations in the test scenario.
Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, backend testing and load testing.
Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, backend testing and load testing.
Labels:
Client server,
Web testing
What is base lining?
Baselining :
Process by which the quality and cost effectiveness of a service is assessed, usually in advance of a change to the service. Baselining usually includes comparison of the service before and after the Change or analysis of trend information. The term Benchmarking is normally used if the comparison is made against other enterprises.
For example :If the company has different projects.For each project there will be seperate test plans.This test plans should be accepted by peers in the organization after modifications.That modified test plans are the baseline for the testers to use in different projects.Any further modifications are done in the test plan.Present modified becomes the baseline.Because this test plan becomes the basis for running the testing project.
Process by which the quality and cost effectiveness of a service is assessed, usually in advance of a change to the service. Baselining usually includes comparison of the service before and after the Change or analysis of trend information. The term Benchmarking is normally used if the comparison is made against other enterprises.
For example :If the company has different projects.For each project there will be seperate test plans.This test plans should be accepted by peers in the organization after modifications.That modified test plans are the baseline for the testers to use in different projects.Any further modifications are done in the test plan.Present modified becomes the baseline.Because this test plan becomes the basis for running the testing project.
Labels:
Base lining
Saturday, July 24, 2010
Difference between gprs and edge technology in mobile phone
Further enhancements to GSM networks are provided by Enhanced Data rates for GSM Evolution (EDGE) technology. EDGE provides up to three times the data capacity of GPRS. Using EDGE, operators can handle three times more subscribers than GPRS; triple their data rate per subscriber, or add extra capacity to their voice communications. EDGE uses the same TDMA (Time Division Multiple Access) frame structure, logic channel and 200kHz carrier bandwidth as today's GSM networks, which allows it to be overlaid directly onto an existing GSM network. For many existing GSM/GPRS networks, EDGE is a simple software-upgrade.
EDGE allows the delivery of advanced mobile services such as the downloading of video and music clips, full multimedia messaging, high-speed colour Internet access and e-mail on the move.
EDGE allows the delivery of advanced mobile services such as the downloading of video and music clips, full multimedia messaging, high-speed colour Internet access and e-mail on the move.
Labels:
EDGE,
GPRS,
Mobile applications
Thursday, July 22, 2010
Differences between Sanity and Smoke testing
SMOKE TESTING:
1. Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
2. A smoke test is scripted, either using a written set of tests or an automated test
3. A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
4. Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
5. Smoke testing is normal health check up to a build of an application before taking it to testing in depth.
SANITY TESTING:
1. A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
2. A sanity test is usually unscripted.
3. A Sanity test is used to determine a small section of the application is still working after a minor change.
4. Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. this level of testing is a subset of regression testing.
5. Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.
Hope these points will help you to clearly understand the Smoke and sanity tests and will help to remove any confusion.
1. Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
2. A smoke test is scripted, either using a written set of tests or an automated test
3. A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
4. Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
5. Smoke testing is normal health check up to a build of an application before taking it to testing in depth.
SANITY TESTING:
1. A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
2. A sanity test is usually unscripted.
3. A Sanity test is used to determine a small section of the application is still working after a minor change.
4. Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. this level of testing is a subset of regression testing.
5. Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.
Hope these points will help you to clearly understand the Smoke and sanity tests and will help to remove any confusion.
Labels:
Sanity testing,
Smoke testing
Subscribe to:
Posts (Atom)