Entries from January 2007 ↓

Way to become a good tester:

Remember these ten rules and I am sure you will definitely gain very good testing skill.

1. Test early and test often.
2. Integrate the application development and testing life cycles. You’ll get better results and you won’t have to mediate between two armed camps in your IT shop.
3. Formalize a testing methodology; you’ll test everything the same way and you’ll get uniform results.
4. Develop a comprehensive test plan; it forms the basis for the testing methodology.
5. Use both static and dynamic testing.
6. Define your expected results.
7. Understand the business reason behind the application. You’ll write a better application and better testing scripts.
8. Use multiple levels and types of testing (regression, systems, integration, stress and load).
9. Review and inspect the work, it will lower costs.
10. Don’t let your programmers check their own work; they’ll miss their own errors.

Basics of WinRunner: 

Difference between WinRunner and Test Director?
“WinRunner handles automation test scripts
TestDirector manages test scripts, defects and test plan”

What is TSL? What 4GL is it similar too?
“Test Script Language, TSL C++”

Intermediate Que

What databases can Test Director reside on?
Oracle, Access, Sybase, MsSQL

Name a couple of standard web function found in the function generator? And explain their purpose.
Web_****

Advance que

Explain data parameterization in WinRunner.
Data is written multiple times, while WinRunner has a repeated loop to process the data.

Explain the project tree in Test Director.
Used to coordinate and manage test cases.

Expert Que

Have you completed the CPS exam? Which one?
TestSuite 6.0, LoadRunner, etc.

Write a short compiled module which selects random numbers; and what function is used to call your customized compiled module? Load or Reload function

What’s the purpose of the wrun.ini file?
Configuration set up for WinRunner

Hope you will enjoy this series of testing interview questions. For more interview questions please visit the posts on software testing interview questions.

I have posted one article on ‘To start with Automation’, now i think i should also
mention some ins and outs of Automation.

· Possibly. For small projects, the time needed to learn and implement them may not be worth it. For larger projects, or on-going long-term projects they can be valuable.

· Test automation can add a lot of complexity and cost to a test team’s effort. In addition problems like including unrealistic expectations, poor testing practices, a false sense of security, maintenance costs, and other technical and organizational problems might arise. But it can also provide some valuable assistance if its done by the right people, in the right environment and done where it makes sense to do so.

· Automated testing is an expensive process. Studies show that it can take between 3 to 10 times longer to develop automated Test Suite than to create and execute manual test cases. Costs of test automation include personnel to support test automation for the long term, dedicated test environment as well as the costs for the purchase, development and maintenance of tools.

· A common type of automated tool is the ‘record/playback’ type. For example, a tester could click through all combinations of menu choices, dialog box choices, buttons, etc. in an application GUI and have them ‘recorded’ and the results logged by a tool. The ‘recording’ is typically in the form of text based on a scripting language that is interpretable by the testing tool. If new buttons are added, or some underlying code in the application is changed, etc. the application can then be retested by just ‘playing back’ the ‘recorded’ actions, and comparing the logging results to check effects of the changes. The problem with such tools is that if there are continual changes to the system being tested, the ‘recordings’ may have to be changed so much that it becomes very time-consuming to continuously update the scripts. Additionally, interpretation of results (screens, data, logs, etc.) can be a difficult task. Note that there are record/playback tools for text-based interfaces also, and for all types of platforms.

Be sure to think these points before going for your project Automation.
So after taking decision for Automation you will not be in trouble.

This is Pavani from Neo Solutions, we are working with various companies, which even include ISO and CMM Level companies. For our Client Bally Technologies, we require QA Testing Professionals.

Interviews at Pune on 20th (Saturday) January 2007

Note :

1. If you are not interested pls. forward this to your friends and colleagues.
2. If you have attended the interview in the Last 3 months then pls. do not send your profile.
3. Candidates who are willing to relocate only send the CVs.

The following is the requirement:

Position : QA Testing – Professionals

Experience Required : 2 to 8 Yrs

Job Locations : Bangalore / Chennai

Interview Location : Pune

Interview Date : 20/01/2007 (Saturday)

Job Specifications:

Exp in writing and executing manual and Automated test cases and scripts
Working knowledge of test case and management applications, such as Test Director / Quality Center, TestLog, Test Case Manager etc.
Design and development of test cases from software design documentation and Functional, technical and regulatory requirements
Design and Development of project test plans as required
Execution of test cases and scripts using manual and automated test methods
Defect identification,! isolation and reporting
Development of defect escape prevention methods
Analysis and reporting of test results
Effective evaluation of test results
Effective evaluation and communication of software fitness
Familiarity with C++, C#, .NET, IP highly desired
Familiarity with Ruby, Visual Basic or other programming / scripting languages desired

If you are interested please send your latest CV along with the following details :

Current CTC :
Expected CTC :
Notice Period :
Total Experience :
Exp. on QA Testing :
Location Preference(Chennai/Bangalore/Both) :
Contact Numbers (Mobile & Residence) :
Feasible Interview Time on 20/01/2007 :
(Available Slots : Slot1 : 10.00 AM; Slot2 : 12.00 AM; Slot3 : 2.00 PM; Slot4 : 4.00 PM)

Thanks and Regards,
Pavani
Technical Recruiter
Neo Solutions
Ph : 040-66828000, 66787555
Cell : 09885260008
itjobs@neosolutionsonline.com

Automation Checklist

If you answer yes to any of these questions, then your test should be seriously considered for automation.

Can the test sequence of actions be defined?

Is it useful to repeat the sequence of actions many times? Examples of this would be Acceptance tests, Compatibility tests, Performance tests, and regression tests.

Is it possible to automate the sequence of actions?
This may determine that automation is not suitable for this sequence of actions.

Is it possible to “semi-automate” a test?
Automating portions of a test can speed up test execution time.

Is the behavior of the software under test the same with automation as without?
This is an important concern for performance testing.

Are you testing non-UI aspects of the program?
Almost all non-UI functions can and should be automated tests.

Do you need to run the same tests on multiple hardware configurations?
Run ad hoc tests (Note: Ideally every bug should have an associated test case. Ad hoc tests are best done manually. You should try to imagine yourself in real world situations and use your software as your customer would. As bugs are found during ad hoc testing, new test cases should be created so that they can be reproduced easily and so that regression tests can be performed when you get to the Zero Bug Build phase.) An ad hoc test is a test that is performed manually where the tester attempts to simulate real world use of the software product. It is when running ad hoc testing that the most bugs will be found. It should be stressed that automation cannot ever be a substitute for manual testing.

Walk In to Join Symantec Corporation on dated 06th Jan 2007, Saturday.

The Symantec R&D division in Pune presents a golden opportunity to put your career on a fast track…

The Opportunities:Symantec R&D is looking for top class testers to work at its state of the art facilities in Pune. If you meet the requirements given below, walk in with a print out of this e-mail (is a must) copy of your latest Resume and salary slip to explore exciting opportunities:

Present Salary.
Expected Salary.
Relocation Constraints (READY TO WORK IN PUNE)
How early can you join.

Requirement:QA Unix – (0.6 – 4 yrs. of exp.)
Hands on experience on Perl/Shell scripting, Test planning, development and execution on Unix/Linux HP-UX, AIX or Solaris platform is a must.
C,C++ development
Excellent knowledge of QA tools/processes
Test case design and development
Experience in storage domain/Veritas products is an added plus.

Qualification-B.E, B.Tech, M.E, M.Tech, BCS, BCA, MCA,C-DAC. (COMPUTER SCIENCE / IT)

The eligibility criteria is that the candidate must have secured a minimum of 55% in the above mentioned degrees.

Event details:Date: 06th Jan 07 (Saturday)Venue : Symantec Corporation Symphony, S No 210A/1, Opp Vrindavan Society,Range Hills, Pune 411020 Time : 09:00 am to 3:00 pm

Selection criteria:• Technical Test• Technical Interview

http://www.symantec.com/about/careers

Email: Kamlesh_borde@symantec.com