Topic: Miscellaneous software testing questions

Message

   1. What type of testing u perform in organization while u do System Testing, give clearly?

Functional testing
User interface testing
Usability testing
Compatibility testing
Model based testing
Error exit testing
User help testing
Security testing
Capacity testing
Performance testing
Sanity testing
Regression testing
Reliability testing
Recovery testing
Installation testing
Maintenance testing
Accessibility testing, including compliance with:
Americans with Disabilities Act of 1990
Section 508 Amendment to the Rehabilitation Act of 1973  Web Accessibility Initiative (WAI) of the World Wide Web  Consortium (W3C)

2. what is the diff b/w funtional testing and integration testing?

Functional testing is testing the whole functioalitiy of the system or the appllication whether it is meeting the functional specifications

Integration testing means testing the functianality of integrated module when two individual modules are integrated for this we use top-down approach and bottom up approach

3.  what is bug, deffect, issue, error?

Bug:–  Bug is identified by the tester.

Deffect:– Whenever the project is received for the  analisys phase ,may be some requirement miss to get or understand most of the time Defect itself come with the
project (when it comes).

Issue :– Client site error most of the time.

Error :– When anything is happend wrong in the project from the development side ie. called as the error ,most of the time this is knowing by the developer.

Bug : a fault or defect in a system or machine

Defect : an imperfection in a device or machine;

Issue : An issue is a major problem that will impede the progress of the project and cannot be resolved by the project manager and project team without outside help

Error :
Error is the deviation of a measurement, observation, or  calculation from the truth

4. what is smoke testing and user interface testing?

ST :Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details. The term comes
to software testing from a similarly basic type of hardware testing.

UIT :I did a bit or R n D on this …. some say its nothin but Usability testing. Testing to determine the ease with which a user can learn  to operate, input, and interpret outputs of a system or component.

Smoke tesing is nothing but to check whether basic  functionality of the build is stable or not? i.e if it possess 70% of the functionality we say build is  stable.
User interface testing: We check all the fields whether they are existing or not as per the format we check speelling graphic font sizes everything in the window present or not.

5. Who will change the Bug Status as Deffered?

Bug will be in open status while developer is working on it Fixed after developer completes his work if it is not fixed properly the tester puts it in reopen After fixing the bug properly it is in closed state. 

6. what is the difference between buglog and defect tracking?

Bug log is a document which maintains the information of the bug where as bug tracking is the process.

7. Difference beween re testing and regression testing?

Retesting : –

reexecution of testcases on same application build with different input values is retesting.

Regression Testting :

reexecution of testcases on modify form of build is called  regression testing..

8. How to execute testcase?

There are two ways:
1. Manual Runner Tool for manual execution and updation of test status.
2. Automated test case execution by specifying Host name and other automation pertaining details.

9. If we have no SRS,BRS but we have test cases does u execute the test cases blindly or do u follow any other process?

Test case would have detail steps of what the application is supposed to do. SO
1) Functionality of application is known.

2) In addition you can refer to Backend, i mean look into the Database. to gain more knowledge of the application

10. Whatz the main use of preparing a traceability matrix?

To Cross verify the prepared testcases and test scripts with user requirements.

To monitor the changes , enhance occured during the development of the project.

Tracebility matrix is prepared in order to cross check the testcases designed against each requirement, hence giving an opportunity to verify that all the requirements are
covered in testing the application.

11. Where you involve in testing life cycle, what type of test you perform?

Generally test engineers involved from entire test life cycle i.e, test plan, test case preparation, execution, reporting. generally system testing, regression testing, adhoc testing
etc

12. Test cases for IE 6.0?

Test cases for IE 6.0 ie Internet Explorer 6.0:—
1)First I go for the Installation side, means that –
+ is it working with all versions of Windows ,Netscape or other softwares in otherwords we can say that IE must check with all hardware and software parts.
2) Secondly go for the Text Part means that all the Text part appears in frequent and smooth manner.
3) Thirdly go for the Images Part means that all the Images  appears in frequent and smooth manner.
4) URL must run in a better way.
5) Suppose Some other language used on it then URL take the  Other Characters, Other than Normal Characters.
6)Is it working with Cookies frequently or not.
7) Is it Concerning with different script like JScript and VBScript.
8) HTML Code work on that or not.
9) Troubleshooting works or not.
10) All the Toolbars are work with it or not.
11) If Page has Some Links, than how much is the Max and Min Limit for that.
12) Test for Installing Internet Explorer 6 with Norton Protected Recycle Bin enabled .
13) Is it working with the Uninstallation Process.
14) Last but not the least test for the Security System for the IE 6.0

13. If project wants to release in 3months what type of Risk analysis u do in Test plan?

Use risk analysis to determine where testing should be focused. Since it’s rarely possible to test every possible aspect of an application, every possible combination of  events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills,  common sense, and experience. (If warranted, formal methods  are also available.) Considerations can include:
•    Which functionality is most important to the  project’s intended purpose?
•    Which functionality is most visible to the user?
•    Which functionality has the largest safety impact?
•    Which functionality has the largest financial impact on users?
•    Which aspects of the application are most important to the customer?
•    Which aspects of the application can be tested early in the development cycle?
•    Which parts of the code are most complex, and thus most subject to errors?
•    Which parts of the application were developed in rush or panic mode?
•    Which aspects of similar/related previous projects caused problems?
•    Which aspects of similar/related previous projects had large maintenance expenses?
•    Which parts of the requirements and design are unclear or poorly thought out?
•    What do the developers think are the highest-risk  aspects of the application?
•    What kinds of problems would cause the worst publicity?
•    What kinds of problems would cause the most customer service complaints?
•    What kinds of tests could easily cover multiple functionalities?
•    Which tests will have the best high-risk-coverage to time-required ratio

14. High sevirity, low prority bug?

A page is rarely accessed, or some activity is performed rarely but that thing outputs some imp. data incorrectly, or corrupts the data, this will be a bug of H severity L priority

15. What is API?

Application program interface.

16. What is risk analysis,what type of risk analysis u did in u r project?

Risk Analysis :
A systematic use of available information to determine how often specified events and unspecified events may occur and the magnitude of their likely consequences
OR
procedure to identify threats & vulnerabilities, analyze  them to ascertain the exposures, and highlight how the  impact can be eliminated or reduced

Types :
1.QUANTITATIVE RISK ANALYSIS
2.QUALITATIVE RISK ANALYSIS

17. What is change request,how u use it ?

Change Request is a attribute or part of Defect Life Cycle.

Now wen u as a tester find a defect n report to ur DL…he in turn informs the Dvpt Team.
The DT says its not a defect its an extra implemnetation or  says not part of req’ment.
its new.cust has to pay.

Here the status in ur defect report would be Change Request

I think change request controlled by change request control  board (CCB). If any changes required by client after we  start the project , it has to come thru that CCB and they
have to approve it. CCB got full rights to accept or reject  based on the project schedule and cost.

18. What do u mean by Positive and Negative testing & whatz r the diff’s between them.Can anyone explain with an example?

Positive Testing: Testing the application functionality with valid inputs and verifying that output is correct

Negative testing: Testing the application functionality  with invalid inputs and verifying the output Difference is nothing but How the application behaves when
we enter some invalid inputs Suppose if it accepts invalid input the application
functionality is wrong

Positive test: testing aimed to show that s/w work ie with valid inputs.this is also called as “test to pass’
-ve testing: testing aimed at showing s/w does’t work. which is also know as ‘test to fail”
BVA is the best example of -ve testing.

19. How can u do the follwing 1)Usability testing 2)scalability Testing

UT :
Testing the ease with which users can learn and use a product.

ST :
Its a Web Testing defn.allows web site capability improvements.

PT :
Testing to determine whether the system/software meets the  specified portability requirements.

20. Whatz the main use of preparing Tracebility matrix and explain the real time usage?

A traceability matrix is created by associating requirements with the work products that satisfy them. Tests are associated with the requirements on which they  are based and the product tested to meet the requirement.

A traceability matrix is a report from the requirements database or repository.

Author	Message
Amrita Groupie Joined: 13Feb2007 Online Status: Offline Posts: 57	Topic: Miscellaneous software testing questions Posted: 20May2007 at 11:02pm
	1. What type of testing u perform in organization while u do System Testing, give clearly? Functional testing User interface testing Usability testing Compatibility testing Model based testing Error exit testing User help testing Security testing Capacity testing Performance testing Sanity testing Regression testing Reliability testing Recovery testing Installation testing Maintenance testing Accessibility testing, including compliance with: Americans with Disabilities Act of 1990 Section 508 Amendment to the Rehabilitation Act of 1973 Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C) 2. what is the diff b/w funtional testing and integration testing? Functional testing is testing the whole functioalitiy of the system or the appllication whether it is meeting the functional specifications Integration testing means testing the functianality of integrated module when two individual modules are integrated for this we use top-down approach and bottom up approach 3. what is bug, deffect, issue, error? Bug:– Bug is identified by the tester. Deffect:– Whenever the project is received for the analisys phase ,may be some requirement miss to get or understand most of the time Defect itself come with the project (when it comes). Issue :– Client site error most of the time. Error :– When anything is happend wrong in the project from the development side ie. called as the error ,most of the time this is knowing by the developer. Bug : a fault or defect in a system or machine Defect : an imperfection in a device or machine; Issue : An issue is a major problem that will impede the progress of the project and cannot be resolved by the project manager and project team without outside help Error : Error is the deviation of a measurement, observation, or calculation from the truth 4. what is smoke testing and user interface testing? ST :Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details. The term comes to software testing from a similarly basic type of hardware testing. UIT :I did a bit or R n D on this …. some say its nothin but Usability testing. Testing to determine the ease with which a user can learn to operate, input, and interpret outputs of a system or component. Smoke tesing is nothing but to check whether basic functionality of the build is stable or not? i.e if it possess 70% of the functionality we say build is stable. User interface testing: We check all the fields whether they are existing or not as per the format we check speelling graphic font sizes everything in the window present or not. 5. Who will change the Bug Status as Deffered? Bug will be in open status while developer is working on it Fixed after developer completes his work if it is not fixed properly the tester puts it in reopen After fixing the bug properly it is in closed state. 6. what is the difference between buglog and defect tracking? Bug log is a document which maintains the information of the bug where as bug tracking is the process. 7. Difference beween re testing and regression testing? Retesting : – reexecution of testcases on same application build with different input values is retesting. Regression Testting : reexecution of testcases on modify form of build is called regression testing.. *8. How to execute testcase?* There are two ways: 1. Manual Runner Tool for manual execution and updation of test status. 2. Automated test case execution by specifying Host name and other automation pertaining details. 9. If we have no SRS,BRS but we have test cases does u execute the test cases blindly or do u follow any other process? Test case would have detail steps of what the application is supposed to do. SO 1) Functionality of application is known. 2) In addition you can refer to Backend, i mean look into the Database. to gain more knowledge of the application 10. Whatz the main use of preparing a traceability matrix? To Cross verify the prepared testcases and test scripts with user requirements. To monitor the changes , enhance occured during the development of the project. Tracebility matrix is prepared in order to cross check the testcases designed against each requirement, hence giving an opportunity to verify that all the requirements are covered in testing the application. 11. Where you involve in testing life cycle, what type of test you perform? Generally test engineers involved from entire test life cycle i.e, test plan, test case preparation, execution, reporting. generally system testing, regression testing, adhoc testing etc 12. Test cases for IE 6.0? Test cases for IE 6.0 ie Internet Explorer 6.0:— 1)First I go for the Installation side, means that – + is it working with all versions of Windows ,Netscape or other softwares in otherwords we can say that IE must check with all hardware and software parts. 2) Secondly go for the Text Part means that all the Text part appears in frequent and smooth manner. 3) Thirdly go for the Images Part means that all the Images appears in frequent and smooth manner. 4) URL must run in a better way. 5) Suppose Some other language used on it then URL take the Other Characters, Other than Normal Characters. 6)Is it working with Cookies frequently or not. 7) Is it Concerning with different script like JScript and VBScript. 8) HTML Code work on that or not. 9) Troubleshooting works or not. 10) All the Toolbars are work with it or not. 11) If Page has Some Links, than how much is the Max and Min Limit for that. 12) Test for Installing Internet Explorer 6 with Norton Protected Recycle Bin enabled . 13) Is it working with the Uninstallation Process. 14) Last but not the least test for the Security System for the IE 6.0 13. If project wants to release in 3months what type of Risk analysis u do in Test plan? Use risk analysis to determine where testing should be focused. Since it’s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include: • Which functionality is most important to the project’s intended purpose? • Which functionality is most visible to the user? • Which functionality has the largest safety impact? • Which functionality has the largest financial impact on users? • Which aspects of the application are most important to the customer? • Which aspects of the application can be tested early in the development cycle? • Which parts of the code are most complex, and thus most subject to errors? • Which parts of the application were developed in rush or panic mode? • Which aspects of similar/related previous projects caused problems? • Which aspects of similar/related previous projects had large maintenance expenses? • Which parts of the requirements and design are unclear or poorly thought out? • What do the developers think are the highest-risk aspects of the application? • What kinds of problems would cause the worst publicity? • What kinds of problems would cause the most customer service complaints? • What kinds of tests could easily cover multiple functionalities? • Which tests will have the best high-risk-coverage to time-required ratio 14. High sevirity, low prority bug? A page is rarely accessed, or some activity is performed rarely but that thing outputs some imp. data incorrectly, or corrupts the data, this will be a bug of H severity L priority 15. What is API? Application program interface. 16. What is risk analysis,what type of risk analysis u did in u r project? Risk Analysis : A systematic use of available information to determine how often specified events and unspecified events may occur and the magnitude of their likely consequences OR procedure to identify threats & vulnerabilities, analyze them to ascertain the exposures, and highlight how the impact can be eliminated or reduced Types : 1.QUANTITATIVE RISK ANALYSIS 2.QUALITATIVE RISK ANALYSIS 17. What is change request,how u use it ? Change Request is a attribute or part of Defect Life Cycle. Now wen u as a tester find a defect n report to ur DL…he in turn informs the Dvpt Team. The DT says its not a defect its an extra implemnetation or says not part of req’ment. its new.cust has to pay. Here the status in ur defect report would be Change Request I think change request controlled by change request control board (CCB). If any changes required by client after we start the project , it has to come thru that CCB and they have to approve it. CCB got full rights to accept or reject based on the project schedule and cost. 18. What do u mean by Positive and Negative testing & whatz r the diff’s between them.Can anyone explain with an example? Positive Testing: Testing the application functionality with valid inputs and verifying that output is correct Negative testing: Testing the application functionality with invalid inputs and verifying the output Difference is nothing but How the application behaves when we enter some invalid inputs Suppose if it accepts invalid input the application functionality is wrong Positive test: testing aimed to show that s/w work ie with valid inputs.this is also called as “test to pass’ -ve testing: testing aimed at showing s/w does’t work. which is also know as ‘test to fail” BVA is the best example of -ve testing. 19. How can u do the follwing 1)Usability testing 2)scalability Testing UT : Testing the ease with which users can learn and use a product. ST : Its a Web Testing defn.allows web site capability improvements. PT : Testing to determine whether the system/software meets the specified portability requirements. 20. Whatz the main use of preparing Tracebility matrix and explain the real time usage? A traceability matrix is created by associating requirements with the work products that satisfy them. Tests are associated with the requirements on which they are based and the product tested to meet the requirement. A traceability matrix is a report from the requirements database or repository. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Beginners @ OneStopTesting