Steps to Import test cases from excel to Test Director

1) Once you login in to TD you will the following options on the top right

hand side of the screen, they are Back, Next, Tool, Help, Logout (in TD 9.0 i am

saying)

2) Select Help, then you will get various options from that select Add-ins page

3) Then you will get a new window with different Add-ins

4) Select the required add-in , it will automatically install in your system

4) Select an Exce or Word file then you fill find an option Export to Quality

center

5) Select required test cases and upload these by using Export to QC option.

What is Referential Integrity???

Referential integrity is a database concept that ensures that relationships between tables remain consistent. When one table has a foreign key to another table, the concept of referential integrity states that you may not add a record to the table that contains the foreign key unless there is a corresponding record in the linked table. It also includes the techniques known as cascading update and cascading delete, which ensure that changes made to the linked table are reflected in the Primary table.

Consider the situation where we have two tables: Employees and Managers. The Employees table has a foreign key attribute entitled ManagedBy which points to the record for that employee’s manager in the Managers table. Referential integrity enforces the following three rules:

1. We may not add a record to the Employees table unless the ManagedBy attribute points to a valid record in the Managers table.
2. If the primary key for a record in the Managers table changes, all corresponding records in the Employees table must be modified using a cascading update.
3. If a record in the Managers table is deleted, all corresponding records in the Employees table must be deleted using a cascading delete.

7 habbits of successful testers

• Self Driven or high levels of Inner drive for learning new things – No fear of unknown.
• Spontaneous – Thinks on the feet – Good in emergency response.
• Agile and adaptable.
• Love for Science (Physics/Chemistry), Mathematics and Philosophy.
• Love for problem, Puzzles.
• Hunger for self Expression – Writing, speaking.
• Organized Skepticism and constantly challenge their own thoughts

Why Counting is Bad Idea?

Let us consider a typical Test report - a report that is presented in a meeting for assessing the progress of testing, attended by key stakeholders and team members:

No of Test cases prepared: 1230
No of Test cases Executed: 345
No of Test cases Failed : 50
No of Bugs reported: 59
No of Requirements Analyzed : 45
No of requirements updated :50
No of Transactions covered in Performance Testing : 24
No of Use cases Tested : 233

Productivity

No of Test cases prepared Per Person Per hour = 5
No of Test cases executed per person per hour = 15


What do you see here?

Managers love numbers - Numbers give objective information, numbers quantify observations and help in taking decisions (??). Numbers simplify things, one can see trends in numbers.

You might have heard about one or more of above statements (mostly in review, progress meetings right?). When it comes to testing, followers of Factory approach testing, are comfortable in just counting things like test cases, requirements, use cases, Bugs, passed and failed test cases etc and take decisions about "quality" of the product.

Why counting (without qualifications) is bad idea in testing? What are disadvantages of such practice? Let us briefly take a look of few famous frequently *counted* things

Count Requirements (as in there are 350 requirements for this project)
Can we count?
How to count? Do we have a bulleted list of requirements? If not, what to do?
How to translate given requirements into "bulleted list"
How to account for Information loss, interpretation errors while counting requirements
Count Test cases ( as in test team has written (or designed or prepared) 450 test cases in last week)
Test cases are test ideas. Test case is only a vague, incomplete and shallow representation of actual intellectual engagement that happens in testers mind at the time of test execution (Michael Bolton, mentioned this in his recent Rapid software Testing workshop at Hyderabad)
How can we count ideas?
Test cases can be counted in multiple ways - more often than not, in a ways that are "manipulative" - count is likely to be misleading
When used for knowing or assessing Testing progress - likely to mislead the management
Count Bugs ( we have 45 bugs discovered in this cycle of testing so far)
The story or background about a bug is more interesting and valuable than the count of bugs ( this again I owe it to Micheal Bolton - "Tell me story about this sev 1 bug? would be more informative and revealing question than asking how many sev 1 bugs we have uncovered so far?
when tied to testers effectiveness - is likely cause testers to manipulate bug numbers ( as in Tester 1 is great tester as he always logs maximum number of bugs)
Let us face the fact of life in software testing - there are certain things in testing that can not be counted as we count no of cars in the parking lot, no of patients visited a dentist's clinic or No of Students in a school.

Certain artifacts like test cases, requirements and bugs are not countable things and any attempt to count them can only lead to manipulations and ill-informed decisions.

Wait --- Are there any things at all in testing that we can count without loss of effectiveness and usefulness of the information that a counted number might reveal?

Testing Interview Questions

Test Automation job interview questions:

1. What automating testing tools are you familiar with?
2. How did you use automating testing tools in your job?
3. Describe some problem that you had with automating testing tool.
4. How do you plan test automation?
5. Can test automation improve test effectiveness?
6. What is data - driven automation?
7. What are the main attributes of test automation?
8. Does automation replace manual testing?
9. How will you choose a tool for test automation?
10. How you will evaluate the tool for test automation?
11. What are main benefits of test automation?
12. What could go wrong with test automation?
13. How you will describe testing activities?
14. What testing activities you may want to automate?
15. Describe common problems of test automation.
16. What types of scripting techniques for test automation do you know?
17. What are principles of good testing scripts for automation?
18. What tools are available for support of testing during software development life cycle?
19. Can the activities of test case design be automated?
20. What are the limitations of automating software testing?
21. What skills needed to be a good software test automator?
22. How to find that tools work well with your existing system?
23. Describe some problem that you had with automating testing tool.
24. What are the main attributes of test automation?
25. What testing activities you may want to automate in a project?
26. How to find that tools work well with your existing system?
27. What are some of the common misconceptions during implementation of an automated testing tools for the first time?

Basic SQA testing questions
1. What is the Difference between Project and Product testing? What difference you have observed while
testing the Clint/Server application and web server application
2. What are the differences between interface and integration testing? Are system specification and functional
specification the same? What are the differences between system and functional testing?
3. What is Multi Unit testing?
4. What are the different types, methodologies, approaches, methods in software testing
5. What is the difference between test techniques and test methodology?

Interview questions on WinRunner

1. How you used WinRunner in your project? - Yes, I have been using WinRunner for creating automated
scripts for GUI, functional and regression testing of the AUT.
2. Explain WinRunner testing process? - WinRunner testing process involves six main stages
o Create GUI Map File so that WinRunner can recognize the GUI objects in the application being
tested
o Create test scripts by recording, programming, or a combination of both. While recording tests,
insert checkpoints where you want to check the response of the application being tested.

WinRunner interview questions
1. Describe the process of planning a test in WinRunner?
2. How do you record a new script? Can you e-mail a WinRunner script? How can a person run a previously
saved WinRunner script?
3. How can you synchronize WinRunner scripts?
4. What is a GUI map? How does it work?
5. How can you verify application behavior?
Other
1. What programming language are you using?
2. What C++ libraries are you proficient with?
3. Which argorithm do you like the most? Why?
4. How do you debug SSH?
5. What is the QA process?
6. How do you train another QA engineer?
7. What bug tracking tools you have used? Have you used any free tools?
8. How do you start your QA if there are no system requirements?
9. Have you used MSVC? What do you think of it?
10. There are 3 lights (in one room) and 3 swtiches (in another room), one for each, if you only enter into the
light room once. How can you find out which switch corresponds to which light?
11. What is your weakness?
12. Why do you think you are suited for this job?
13. If there is a day, when you find yourself not fitting in our team, what will you do?
14. What makes you think you are qualified for this job?
15. Do you like music? Which composers are your favourite?
16. What kind of PC games you like most? Why?
17. Are you familiar with collboration tools? Which communication method do you prefer for talk, email and
chat?
18. When will you be available to start work?
19. What security tools have you used?
20. Tell me about yourself.
21. Tell me about your experience with this type of work
22. What do you like and dislike about our company?
23. Why do you want to work for us?
24. What should we hire you? What can you do for us? What can you do that others can not?
25. What is the job’s most attractive and least attractive factor?
26. What do you look for in a job?
27. Please give me your definition of software test engineer.
28. How long would it take you to make a meaningful contribution to our firm?
29. How long would you stay with us?
30. Are you thinking of going back to school or college?
31. What kind of programs/machines or equipment have you worked with?
32. You may be overqualified for this position we have to offer.
33. Give me an example of a project you handled from start to finish.
34. What was your last employer’s opinion of you?
35. Can you work under pressure, deadline etc?
36. Do you have any questions?
37. What is it you liked and disliked about your last job?