My other Blogs
Hi.. I will be posting all the testing related stuff here. The content posted here is a collection from different websites.
Saturday, June 14, 2008
Preparing for an interview?
All the questions listed here are someone's experiences in an interview:
1. What is difference between Utf16 and utf8?
2. If I created an application with .pcs extension how will u test in IE?
3. How will you test login page? Can we apply sql injection there?
4. How will you change java script in IE?
5. Can IE 3.,IE 4,IE 5,IE 6 work simultaneously on same computer?
6. what is ssl and ssh?
7. What is xss?
8. .If I wrote a program , that has to work for Korea language but it is showing English words in the application ?what might have gone wrong?
9. write a program for palindrome in java? (logic!!!!!)?
10. What is content advisor?
11. what are various layers in osi model explain them briefly ?
12. Tell me about your self?
13. What is normalization?
14. What are are types of joins?
15. How to get second max salary?
16. What is difference between test harness and test suite?
17. What is localization and globalization?
18. Write a program to find max and min of a number in c?
19. What are test case and a test plan?
20. What is registry?
21. What is Cambridge application?
22. what is E3
23. What is java script?
24. What is xml?
25. What is html?
26. What are http and https and ssl?
27. What is brief case?
28. How Google search works?
29. What is the sever bug you found?
30. Is it really a bug?
31. How does u measure your performance?
32. What is web server?
33. What is web browser?
34. What is DNS?
++++
35. Tell me about Cambridge application?
36. What are spiders and crawlers?
37. What is localization and internationalization?
38. What is utf16 and utf8?
39. How do you evaluate your performance?
40. What is web server?
41. How do an org know that their page is viewed? (logs)
42. How can u select all the files starting with test in Linux?
43. How does grep command works?
44. Tell about your self?
45. Why you are interested in testing?
46. Explain about your current project?
47. Explain about your role and responsibility in your project?
48. What is the most difficult bug you ever found?
49. Was that a bug?
50. How to kill a process in windows with out using UI (i.e. Task Manager)?
51. How can you do that in LINX OS?
52. How do you change the DATE of the computer system with out using UI (i.e. At command prompt)?
53. What is your favorite programming language?
54. (I answered as JAVA) So why JAVA and why not C or C++?
55. Write a snippet in java to find out the MAX and MIN from a list of numbers?
56. Write a java snippet to read the ASCII characters?
57. What are the different operating systems you are familiar with?
58. What are differences between WIN 98, XP, 2000?
59. What are the differences between HTML and XML?
60. What are the differences between GET and HEAD methods?
61. What are the differences between Localization and internationalization?
62. What are the differences between authorization and authentication?
63. How do you test a Login page which contains a username and password fields and a submit button?
64. If you are a Test Manager, How do you limit the size of password and username fields?
65. Write the test cases for a Telephone?
66. How do you improve your computer performance while you are testing an application?
67. Did you ever write a Test Plan? ( I said “YES”)
68. So, what did you wrote in a test plan?
69. How do you develop a test case?
70. What are the different browsers you are familiar with? And what versions did you used?
71. Did you ever found a P0 bug?
72. What is E3? And describe it?
++++
1. Tell me about your current project?
2. Tell me about your roles in testing your project?
3. Tell me about your self?
4. What is a cookie?
5. What is java script?
6. How can developer handle the situation if the script is disabled?
7. Where do you disable the script?
8. What are test cases for yahoo messenger?
9. What is sql injection?
10. What is registry?
11. What is Linux shell scripting?
12. What is firewall and proxy?
++++
Some more general questions are listed here:
++++
1. How web s erver works
2. How search engine works?
3. How do you test google seawrch engine
4. How do you test Login page?
5. some brief testcases to test security?
6. What is cross site4 scripting?
7. Various testing defns
8. Test case formats, bug reporting format,
9. How do you track testing of applications?
10. How do you ensure that testing is enough for an application?
11. Like these kind of practical questions , but suerly on WEB application
12. How do you test Javascript?
13. Tell me about your self?
14. Explain your Roles and responsibilities in various projects?
15. Frequently Asked Questions:
16. Brief testcases on Wall clock, Monitor, Bottle, Cup, Pen?
17. How do you test the Windows Update process?
18. List the testcases for a Login page ?
19. Write various testcases to test a NotePad and how do you perform Load test?
20. How do you test the desktop calculator?
21. Brief Windows Registry
22. What is Spyware?
23. What is HTTP,HTTPS and WebServer? Also list their default ports?
24. What is the difference between JPEG and BMP files.
25. What is the difference between WAVE and MP3 files?
26. How do you report a bug?
27. What is a firewall?
28. What do know about Virus, Worm and Trojan?
29. How is the security works between Browser and Webserver(Certificate)?
30. What is the difference between Process and Thread? Give an example?
31. What is MultiTasking, Multiprocessing and Multithreading?
32. What is Paging and Indexing?
33. How do you test DeskTop applications?
34. How do test the Installations?
35. What are various Protocols and their communication ports?
36. How do test the Winamp software?
37. what is the difference between rendezvous point and correlation point in winrunner?
38. what is Normalization and explian 3rd normal form?
39. what is the difference between ‘C’ structure and ‘C++’ structure?
40. what is the ‘localization testing’?
41. Difference between .EXE and .DLL?
42. Difference between boxing and un boxing?(.Net or Java 1.5)?
43. Difference between load and stress testing?
44. what is byte code?
45. what is over loading and over ridding?
46. what is the difference between C++ and Java?
47. Describe the verification and validation process?
48. How can you access/change username and password of windows users?
49. Command to find Linux version, IP Address?
50. What's the length of IP Address?
51. What is the difference between History/Cache/Cookies?
52. Write SQL queries to find Higest and second higest salaries of an employee?
53. What is the difference between far pinter and near pointer?
54. Progarms:
55. What is your approach to find length of linked List?
56. Write a program to find Maximum number from a given 'n' numbers?
57. Give an approach to find the repetitive words in a given string and their count?
58. Tell what you know about OOPS with examples?
59. Google interview questions
60. second highest salary: [using sql server]
61. select max(unitprice) from SubProducts where unitprice<(select max(unitprice) from SubProducts)
62. second highest salary:[using mysql]
63. select personid,hourlyrate from Salary order by hourlyrate desc limit 2;
64. what is the difference between rendezvous point and correlation point
65. in winrunner?
66. what is the third normal form DBMS?
67. what is the difference between ‘C’ structure and ‘C++’ structure?
68. what is the ‘localization testing’?
69. difference between boxing and un boxing?
70. difference between .EXE and .DLL?
71. how do u debug windows application?
72. difference between HTTP/HTTPS?
73. why test plan needed in testing?
74. what fields u include in ‘bug tracking tool’?
75. difference between load and stress testing?
76. write test cases for ‘Down loading and install real player software
77. in local machine’?
78. write test cases for standalone system?
79. what is the difference between process and thread?
80. discribe the verification and validation process?
81. OOPs concepts?
82. what is byte code?
83. how u automate ‘SQl injection’ through winrunner?
84. what is over loading and over ridding?
85. what is the difference between C++ and Java?
86. difference between virus/worm/trojen?
87. what protocols u know?
88. --------------------
89. 3nf
90. rendozouse and correlation point
91. c structure & c++ structure
92. localization & globalization testing
93. boxing & unboxing
94. .exe and .dll
95. how do u debug windows app
96. y test plans required
97. diff between http & https
98. how do u create table in oracle 9
99. com/process/dcom/beans
100. test cases for winword/paint
101. test cases for - how do u write test cases for installation of application
102. how do u test word app in browser
103. diff between overloading and overriding
104. db2., mssql
105. virus,worm,trojan
106. removing paint
107. protocols used oops cob
108. ipv4
109. byte code
110. process/thread
111. comm to c kernal
112. what factors u consider for bug tracking tool
113. diff between load and stress
114. ever bug found by u
115. sql injection
116. what type of linux version u r working on
117. linux config - ifconfig
118. excel,calc,media player
119. what type of tests
120. diff b/w .exe, .dll
121. how do u debug .exe file
122. how do u test/debug web service
123. what type of testing tool ur using
124. can u open msaccess file through excel
125. api
126. regtry,install wrd,pe n
127. .net arch,c shrp,.net perf diff
++++
some questions on java:
1)What is OOPs?
2)what is the difference between Procedural and OOPs?
3)What are Encapsulation, Inheritance and Polymorphism?
4)What is the difference between Assignment and Initialization?
5)What are Class, Constructor and Primitive data types?
6)What is an Object and how do you allocate memory to it?
7)What is the difference between constructor and method?
8)What are methods and how are they defined?
9)What is the use of bin and lib in JDK?
10)What is casting?
11)How many ways can an argument be passed to a subroutine and explain them?
12)What is the difference between an argument and a parameter?
13)What are different types of access modifiers?
14)What is final, finalize() and finally?
15)What is UNICODE?
16)What is Garbage Collection and how to call it explicitly?
17)What is finalize() method ?
18)What are Transient and Volatile Modifiers?
19)What is method overloading and method overriding?
20)What is difference between overloading and overriding?
21) What is meant by Inheritance and what are its advantages?
22)What is the difference between this() and super()?
23)What is the difference between superclass and subclass?
24) What modifiers may be used with top-level class?
25)What are inner class and anonymous class?
26)What is a package?
27)What is a reflection package?
28)What is interface and its use?
29)What is an abstract class?
30)What is the difference between Integer and int?
31)What is a cloneable interface and how many methods does it contain?
32)What is the difference between abstract class and interface?
33) Can you have an inner class inside a method and what variables can you access?
34) What is the difference between String and String Buffer?
35) What is the difference between Array and vector?
36) What is the difference between exception and error?
37) What is the difference between process and thread?
38) What is multithreading and what are the methods for inter-thread communication and what is the class in which these methods are defined?
39) What is the class and interface in java to create thread and which is the most advantageous method?
40) What are the states associated in the thread?
41) What is synchronization?
42) When you will synchronize a piece of your code?
43) What is deadlock?
44) What is daemon thread and which method is used to create the daemon thread?
45) Are there any global variables in Java, which can be accessed by other part of your program?
46)What is an applet?
47)What is the difference between applications and applets?
48)How does applet recognize the height and width?
49)When do you use codebase in applet?
50)What is the lifecycle of an applet?
51)How do you set security in applets?
52)What is an event and what are the models available for event handling?
53) What are the advantages of the model over the event-inheritance model?
What are Vector, Hashtable, LinkedList and Enumeration?
++++
Friday, March 30, 2007
Understanding Use Case Modeling
To successfully apply use case diagrams, we must first understand the types of elements used in use case diagrams.
Actors
Actor classes are used to model and represent roles for "users" of a system, including human users and other systems. Actors are denoted as stick person icons. They have the following characteristics:
- Actors are external to a system.
- Actors interact with the system. Actors may use the functionality provide by the system, including application functionality and maintenance functionality. Actors may provide functionality to the system. Actors may receive information provided by the system. Actors may provide information to the system.
- Actor classes have actors instances or objects that represent specific actors.
Figure 1 shows a project management system with a project manager actor and a project database actor. The project manager is a user who is responsible for ensuring the success of project and uses the system to manage projects. The project database is a system that is responsible for housing project management data.
Figure 1
Use Cases
Use case classes are used to model and represent units of functionality or services provided by a system (or parts of a system: subsystems or classes) to users. Use cases are denoted as ellipses or ovals. They may be enclosed by a system boundary or rectangle labeled with the name of the containing system. They have the following characteristics:
- Use cases are interactions or dialogs between a system and actors, including the messages exchanged and the actions performed by the system. Use cases may include variants of these sequences, including alternative and exception sequences.
- Use cases are initiated by actors and may involve the participation of numerous other actors. Use cases should provide value to at least one of the participating actors.
- Use cases may have extension points that define specific points within an interaction at which other use cases may be inserted.
- Use case classes have use case instances or objects called scenarios that represent specific interactions. Scenarios represent a singe sequence of messages and actions.
Figure 1 shows a project management system which provides the functionality to manage projects in which the project manager and project database participate.
Relationships
Association relationships between actor classes and use case classes are used to indicate that the actor classes participates and communicates with the system containing the use case classes. Association relationships are denoted as solid lines or paths. Arrowheads may be used to indicate who initiates communication in the interaction. If an arrowhead points to a use case, the actor at the other end of the association initiates the interaction with the system. If the arrowhead points to an actor, the system initiates the interaction with the actor at the other end of the association.
Figure 1 shows a project management system that provides functionality to manage projects. A project manager initiates this functionality and the system initiates the communication with the project database in providing this functionality.
Includes relationships from base use case classes to inclusion use case classes are used to indicate that the base use case classes will contain the inclusion use case classes; that is, the base use case will contain the inclusion use case. A base use case defines the location at which the inclusion use case is included. Includes relationships are denoted as dashed lines or paths with an open arrow-head pointing at the inclusion use case and are labeled with the <
Figure 2 shows that a project manager may add projects and remove projects using the project management system. When removing projects, the functionality of finding a project is included into removing a project.
Figure 2
Extends relationships from extension use case classes to base use case classes are used to indicate that the base use case classes may be augmented by the extension use case classes; that is, the inclusion use case will augment the base use case if an extension condition is satisfied. A base use case defines the extension point. An extension use case defines the extension condition that must be satisfied in order to insert the extension use case into the base use case. The insertion of the extension use case involves the execution of the base use case up to the extension point, testing the extension condition and inserting and executing the extension use case if the condition is satisfied, and then continuing with the execution of the base use case. Extends relationships are denoted as dashed lines or paths with an open arrow-head pointing at the extension use case and are labeled with the extension condition in square brackets, the <
Figure 3 shows that a project manager may update projects using the project management system. When updating projects, a project manager may manage tasks if the project manager selects the task option, and a project manger may manage resource if the project manager selects the resource option.

Figure 3
Generalization relationships from specialization use case classes to generalized use cases classes are used to indicate the specialization use case classes are consistent with the generalized use case classes and may add additional information. A specialization use case may be used in place of a generalized use case and may use any portions of the interaction of the generalized use case. Generalization relationships are denoted as solid lines or paths with a hollow arrow-head pointing at the generalized use case.
Figure 4 shows that a project manager may publish a project schedule by sending e-mail to project team members using an e-mail system or by generating a web-site on a web-site host. In either case, there will be common functionality used from the generalized use case, for example: inputting project name, extracting the relevant project information form the project database, etc.

Figure 4
Generalization relationships from specialization actor classes to generalized actor classes are used to indicate the specialization actor classes are consistent with the generalized actor classes and may add additional information. A specialization actor may be used in place of a generalized actor and receives the characteristics of the generalized actor. Generalization relationships between actors are denoted similarly to generalization relationships between use cases.
Figure 4 shows that there are two types project mangers, full-time and part-time, and that there are two types of project database, relational database management systems (R-DBMS) and object oriented database management systems (OO-DBMS). Any type of project manager may publish a project schedule using any type of project database.
Use Case Modeling
To successfully apply use case diagrams in use case modeling, we ought to be aware of various guidelines (lessons learned) from applying this technique.
Actors
When modeling actors, we ought to be aware of the following guidelines:
- Actors should be named using noun phrases.
- Actors should be described, indicating what interests an actor has in interacting with the system. For example, the project manager is responsible for ensuring the success of projects, and the project database is responsible for housing project management data.
- Actors define the scope of a system and identify those elements that reside at the periphery of the system and those elements on which the system depends. For example, these use case diagrams indicate that the project management system depends on a project database to provide functionality to a project manager, both residing on the periphery of the system.
Furthermore, other guidelines may be applied in addition to those above.
Use Cases
When modeling use cases, we ought to be aware of the following guidelines:
- Use cases should be named using verb-noun phrases.
- Use cases should be described, indicating how they are started and end, any conditions that must be satisfied before the use case starts (pre-conditions), any conditions that must be satisfied when the use case ends (post-conditions), the sequence of exchanged messages and performed actions, the data exchanged, and any non-functional characteristics (reliability, performance, supportability, etc. constraints). This descriptions may be captured using text and other UML diagrams.
- Use cases define the scope of a system and define the functionality provided by the system and those elements on which the system depends in order to provide the functionality. For example, these use case diagrams indicate that the project management system provides functionality to mange projects to a project manager, and this functionality is implemented using the project database.
- Use cases should facilitate actors in reaching their goals. Use cases are system functionality or responsibilities (requirements) that actors use in order to reach or satisfy their goals. Use cases are not simply actor goals. For example, a project manager is responsible for ensuring the success of projects, and a project database is responsible for housing project management data. The project management system provides functionality to manage projects to a project manager such that the project manger can ensure the success of projects.
- Use cases should facilitate the architecture of a system. Use cases may be organized and partitioned using includes, extends, and generalization relationships to identify, extract, and manage common, optional, and similar functionality. The organization of a set of use cases is not simply the architecture of the system. However, the architecture of a system is based upon the various technology, infrastructure, etc. considerations relevant to satisfying the use cases. For example, the project management system must interface with an e-mail system and a web-site host, thus appropriate subsystem elements must exist within our architecture to facilitate these interfaces.
- Use cases provide flexibility and power throughout the life-cycle process. They provide the freedom to work with a use case as a whole or any subset of a use case via scenarios. The use of includes, extends, and generalization relationships to identify, extract, and manage common, optional, and similar functionality provides further flexibility in working with use cases. Furthermore, use cases may be used to model interactions between actors and systems, subsystems, and classes at various levels of abstraction. This flexibly and power is propagated to every application of use cases. For example, if time, resources, or funding are not sufficient to implement a whole use case, various scenarios may be selected for implementation based upon these factors.
- Use cases may be used as the basis for planning. Time and resource estimates may be associated with use cases. If estimates for a use case cannot be derived, estimates for each scenario of a use case may be derived and used to potentially estimate the overall time and resource estimates for the use case as a whole. This helps ensure that planning is done with the objective of satisfying the requirements.
- Use cases may be used as the basis for analysis, design, and implementation. The sequence of exchanged messages and performed actions within the description of a use case are analyzed and the system is design and implemented to specifically realize use case interactions. This helps ensure that every element of a system is created and used because it contributes to satisfying the requirements.
- Use cases may be used as the basis for testing. The sequence of exchanged messages and performed actions within the description of a use case may be used as test scripts for validating the functionality of a system. This helps ensure that the system is tested and validated against the requirements.
- Use cases may be used as the basis for documentation since use cases capture how users will use the system.
Furthermore, other guidelines may be applied in addition to those above.
Conclusion
As the Unified Modeling Language (UML) is an evolutionary general-purpose, broadly applicable, tool-supported, and industry-standardized modeling language for specifying, visualizing, constructing, and documenting the artifacts of a system-intensive process, by understanding the types of elements used in use case diagrams and being .aware of various guidelines (lessons learned) from applying this technique, we have a sound foundation for successfully applying the technique. Furthermore, it is experience, experimentation, and application of the standard and its various techniques that will enable us to realize its benefits.
Monday, October 30, 2006
Difference b/w Error ,Defect and Bug
Here is some difference, please correct me If I'm wrong.
Error : The Error is the mistakes which is mainly found while writing the code program by the developer. like syntax error, logical error etc.
Defects : Which is founded or traced by the client side while using or checking.
Bug : Bug refers where expected result is not equals to the actual result, and it's affects on the output of the program.
video on boundary testing
Hello my friends,
Here is also a video on boundary testing available by James Bach + Mike Kelley:
http://www.testingr
Tracebility Matrix
Hi Friends,
Traceability matrix is a powerful tool, not just another Excel or Word
Document.
You would have a set of Requirements to start with in any project.
Each of the requirement is checked whether it has been covered in the
Analysis Phase, Design Phase, Coding Phase, Testing phase, Bug
Tracking etc...
All this is done to make sure the set of requirements (Functional and
non-Functional) are delivered as expected by the client.
Instead of giving the field names directly, I have given a link to
another site.
http://www.jiludwig
What are 'Stubs' and 'Drivers' ?
Stub: A piece of code that simulates the activity of missing components.
Driver: A piece of code that passes test cases to another piece of code.
An Example: Consider an example in which we need to develop a "calculator" that converts between different units (e.g., feet to inches).