Subscribe: Testing Jobs Guide
Added By: Feedage Forager Feedage Grade B rated
Language: English
automation  object repository  object spy  object  objects  properties  qtp  repository  rights testingjobsguide  test  testing 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Testing Jobs Guide

Testing Jobs Guide

Guides you to be a successful Test Engineer

Updated: 2018-03-08T20:45:50.889+05:30


Software Testing Interview Questions At IVY Comptech,Hyderabad


STE position for 2+ exp guy.Total 1 round he attended and it took 40 min around to cover all the basic topics on manual and automation testing.Interviewer was very cool and he is more comfortable with manual testing and concerned about the process and the real time life cycle.

  1. Tell me about yourself?
  2. Your current project architecture.
  3. What is White box & Black box?Diff b/w them?
  4. How QTP recognizes the objects?
  5. What if the object properties change compared to recording?Run fails?
  6. Given a simple election application form and asked to write min number of functional test cases to cover the whole form functionality?
  7. Why automation?What do you get from it?
  8. How to reduce the project budget?
  9. When we need to go for descriptive programming in QTP?

What are Test Objects?


Objects that are used in the recording and their properties are stored in the Object Repository. These stored objects are called test objects. The test objects represent objects of the application in the test. During a test run, QuickTest uses these test objects
to identify objects in the application.

You can delete objects from the Object Repository. You can add or remove properties of an object and change the values of those properties.


Test objects can be stored in two types of object repositories: shared and local. By default, the test objects are stored in the local object repository. These test objects are associated with a specific action and no other action can access these objects.

  • You can choose to store your objects in the shared object repository, which can be accessed by multiple tests.
  • Test objects are different from Run-time objects.You can all these properties in Object Spy.

What is Object Spy? How to use it?


The Object Spy feature enables you to view the properties and their current values as
well as methods associated with an object. Object Spy also enables you to view the
syntax for a selected method.



  1. On the QuickTest Professional toolbar, click OBJECT SPY.
  2. Select TOOLS → OBJECT SPY.

To view the run-time properties of an object using the Object Spy:

1. On the QuickTest Professional toolbar, click OBJECT SPY. The OBJECT SPY dialog
box appears.
Note: Alternatively, select TOOLS → OBJECT SPY.
2. In the OBJECT SPY dialog box, click the pointing hand button.
3. With the pointing hand, click on the desired object in the AUT.
4. In the OBJECT SPY dialog box, click the PROPERTIES tab to view the properties of
the selected object.

Imp Note:

  • Test object properties of the actual object are available for all types of objects. This is what you always see in the
    Object Repository. The list shows values when the object was learned.
  • Run-time properties are available for Web, ActiveX, .Net, and Java objects. These may be different from the test
    object properties because object properties change during run-time.

Testing Interview Questions at Sapient,Bangalore


Some of the questions asked for 2+ guy for QA position at Sapient,A CMM Level company.Total 5 rounds at the company including 3 Technical on manual and automation testing and 2 HR rounds.

1. What will happen if i select all the add-ins in QTP at a time?

Answer: Select only the add-ins that you need for the current test. Selecting all available add-ins can cause QuickTest
Professional internal inconsistencies which may lead to test failures.

2. What are the default and optional add-ins available in QTP?


Default:ActiveX,Visual Basic and Web

Optional: The optional add-ins include Java, .NET, Oracle, PeopleSoft, SAP, Siebel, Terminal Emulator, Visual Age Smalltalk
and Web Services.

3. Differences between Global and Action sheets in Data table?

Answer: Simple difference here b/w these two is:

Global Sheet:Can be accessible for all the actions in the entire Test.

Action Sheet: Will be accessible only for that action.Other actions can’t use data in this action sheet.

4. What is Active Screen?

5. Why we need Automation testing?

6. Diff b/w QTP & Win Runner?

7. In how many ways you can insert check points.

Answer: We can insert check points in 4 ways: Through Insert menu,Right click in Keyword View,Right click in Expert view,Right click in Active screen.

8. General Elements/Options in a bug report?

9. What test plan should contain?

10. Diff b/w Test Plan and Test Strategy?

Hope this help you some way! Don't forget subscribe to get daily interview questions by mail.


QTP Interview at ProKarma,Hyderabad


Hello Guys,

Here are some of the questions asked at ProKarma company,Hyderabad.The post was for a 2+exp guy with atleast 1 year QTP experience.

  1. Tell me about your self?
  2. What framework you use in your project?
  3. How do you connect QTP with Database?
  4. How do you connect QC & QTP?
  5. Rate yourself in VB Scripting from 1 to 5 ?
  6. How often you do descriptive programming in your project?
  7. Most difficult bug you found in your project?
  8. If i give you a project and ask to start from today.And you will be only the person in project.How would you start the day?
  9. In how many ways you can play with Synchronization point in your script?
  10. Can you write a script to fill the username and password fields in an application?
  11. What is the Object Repository maximum size?
  12. Why do we need descriptive programming?though we have record and playback.
  13. Why you are looking for a change?
Well these are questions i gathered from the person who attended this interview.He said interviewer was very cool and asked simple questions.He concentrated more on Descriptive programming with VB Script.

Hope you enjoyed! And useful for you!

Don't miss any article:Get it by E-mail(image)

Database Checkpoint and Workflow in QTP?


You can use an application to retrieve data from a database or to insert data into the
database. Database checkpoints in a test enable you to ensure that the application
successfully retrieves or inserts data into a database.

A database checkpoint stores the expected data and compares the expected data with the
data stored in the database. You use a database checkpoint to confirm that the data
stored in a database has not introduced errors in the application.

When executing a database checkpoint, the following events occur:
1. The test arrives at the database checkpoint step and connects to the database.
2. QuickTest sends a query to the database to retrieve the actual data.
3. QuickTest gathers the result set of the query, which provides the actual data.
4. QuickTest compares the actual data with the expected data, which is stored in the database checkpoint, to determine if the test passed or failed.


What is a custom checkpoint?


A custom checkpoint is used to capture and verify dynamic values by using output
parameters, setting the checkpoint on a property of the parameter field, validating
the outcome of a test as acceptable or unacceptable using conditional statement, and
applying REPORTEVENT to report if the outcome is acceptable.


You use a custom checkpoint to:

  • Verify dynamic values in the test using output parameters.
  • Validate the test outcome as acceptable or unacceptable by using a conditional
  • Add a REPORTEVENT to report if the test outcome is acceptable.

What are Break Points in QTP?


Break Point: Stops a test run at a specific step in the test. A red icon appears in the left margin of the step to indicate that a breakpoint is inserted on the step. The test runs until it reaches the breakpoint. You can examine or manipulate steps up to the breakpoint.

Insert/Remove BreakPoint: Debug menu->Insert/Remove BreakPoint (F9)

Enable/Disable BreakPoint: Debug menu->Enable/Disable BreakPoint (Ctrl+F9)

Clear All BreakPoints: Debug menu->Clear All BreakPoints (Ctrl+Shift+F9)

Enable/Disable All BreakPoints: Enables or disables all breakpoints within a test.


What are Step Into,Step Over and Step Out in QTP?


STEP INTO: Runs the current step of the active test. If the current line calls another
action, the called action is displayed. The test pauses at the first line of the called

STEP OVER: Runs the current step in the active test. When the current step calls
another action, the called action is executed but not displayed.

STEP OUT: Runs the current step until the end of the function, returns to the calling
component or function library, and then pauses the run session.

Don't miss any article:Get it by E-mail(image)

Benefits of Automated Testing


(image) (image) (image) Automated testing enables you to optimize software quality, accelerate the testing
process, and increase the testing efficiency.

Automated testing offers the following advantages that are not offered by manual
  1. Reusability: The tests that you automate can be reused during different phases ofthe testing process.
  2. Consistency: Automated tests provide the same test results every time. Therefore,you use automated tests for regression testing.
  3. Productivity: Automated testing enables you to run tests unattended. Therefore,human resources that are otherwise involved in the testing process can be used for accomplishing other tasks and the overall testing productivity of your organization increases.
Don't miss any article:Get it by E-mail(image)

QTP Step Generator Functions


QTP Step Generator Functions:GetROProperty,GetTextLocation,GetTOProperties,GetTOProperty,SetTOProperty

These are most important and confusing to here am sharing you in easy way with syntax and examples too.

GetTOProperties:Returns properties and values which QTP has recorded and will use to identify an object at run time

Syntax: set a=Window("Flight Reservation").WinRadioButton("Business").GetTOProperties

GetTOProperty:It will Return the value of a particular property for a test object which QTP recorded to identify an object during Run time. The value is taken from the Object Repository.

Syntax: set a=Window("Flight Reservation").WinRadioButton("Business").GetTOProperty

GetROProperty: It will Return the current value (run time value) of the test object property from the object in the application.GetROProperty retrieves the current property value of the object in the application during the test run.

Syntax: set a=Window("Flight Reservation").WinRadioButton("Business").GetROProperty

Detailed explanation with example is there here.

SetTOProperty: Sets the value of the specified property in its test object description.It helps to Modify Test Object Properties During a Run Session.

You can modify the properties of the temporary version of the object during the run session without affecting the permanent values in the object repository by adding a SetTOProperty statement in the Expert View.

Syntax:Object(description).SetTOProperty Property, Value

GetTextLocation: Checks whether the specified text string is contained in the specified window area.

Syntax:object.GetTextLocation (TextToFind, Left, Top, Right, Bottom, [MatchWholeWordOnly])

Hope you enjoyed knowing all these.Subscribe to my feeds to get daily updates on testing.

Advertisement:Zoom Into Tech & Blogging tips at TechZoomIn


QTP Certification Sample Q & A’s


1) The new Object Repository Comparison Tool is accessible from the Object Repository Manager. You can use this tool to identify the differences between objects in ........ A) two specified shared object repository files. B) a Shared and a Local object repository files. C) either Shared or Local object repository files. D) two specified Local object repository files. 2) You can use the objects and methods of the QuickTest .................... to write scripts that automatically manipulate object repositories, instead of performing these operations manually using the Object Repository Manager. A) Automation object model B) Object Repository automation object model C) Object Repository model D) Object Repository Script Object model 3) You must convert object repository files from QuickTest Professional 8.2.1 or earlier to the current format before you can use them in QuickTest Professional 9.0 or later. Which method lets you do so. A) Conversion method B) Converge method C) Convert method D) None 4) You open the Object Repository window for a specific component by choosing .......... A) Resources > Object Repository B) Tools > Object Repository C) File > Object Repository D) Help > Object Repository 5) In QTP 9 or above, Test objects can be stored in two types of object repositories—........ A) a shared object repository and a Per-Action object repository. B) a shared object repository and a local object repository. C) a shared object repository and a Action object repository. D) Both A & C 6) The Object Repository Manager enables you to open ...... shared object repositories and modify them as needed A) multiple B) three C) two D) Seven 7) ........ Method Loads the specified object repository. A) Overload B) Load C) Both A & B D) None 8) An object repository that is currently open by another user is locked, is it possible to merge a locked object repository. A) Yes B) No 9) You can manage the shared object repository associations of a selected test using the ............ A) Associate Repositories dialog box B) Object Repositories dialog box C) Associate Repositories Manager dialog box D) Object Repositories Manager dialog box 10) All changes you make to an object repository are automatically updated in all components open on the same computer that use the object repository as soon as you make the change—even if you have not yet saved the object repository with your changes. A) True B) False 11) If you want to modify an object stored in a shared object repository, you can modify it....... A) using the Object Repository Manager B) you can modify it locally using the Object Repository window. C) Both A & B D) None of above 12) ................ Returns an ObjectRepositories collection representing all object repository files associated with the action. A) Object Property B) Automation Object Model C) ObjectRepositories Property D) OR PropertyAnswers Answers: 1) a 2) b 3) c 4) a 5) b 6) a 7) b 8) a 9) a 10) a 11) c 12)c Copy Rights by TestingJobsGuide [...]

50 QTP Certification Q & A’s


1. The toolbar enables you to view the details of an individual action or the entire test flow is 1. Testing toolbar 2. None of the above 3. Action toolbar 4. Test Pane ANSWERE: 3 2. The key that is used to Start/End analog recording mode ? 1. F3 2. SHIFT+ALT+F3 3. CTRL+SHIFT+F3 4. F10 ANSWERE: 2 3.QuickTest supports virtual object for anolog or low-level recording. 1. False 2. True ANSWERE: 1 4. To use a specific property to identify your object, but that property is not listed in the properties list. Then how do you identify that object? 1. Add the specific property to the list 2. Use the Default property 3. Use some other property to identify your object ANSWERE: 1 5. The checkpoint used to check the alt attribute exists for all relevant objects (such as images) is 1. DataBase CheckPoint 2. Accessibility checkpoint 3. Bitmap checkpoint 4. Standard checkpoint ANSWERE: 2 6. Bitmap checkpoint is supported in VB environment. 1. True 2. False ANSWERE: 1 7.Can we parameterize the checkpoints properties? 1. No 2. Yes ANSWERE: 2 8. What is the shortcut key that is used for a Standard Checkpoint? 1. F12 2. F2 3. F10 4. F7 ANSWERE: 1 9.Can we change name of checkpoint? 1. No 2. Yes ANSWERE: 1 10. To compares the values of the specified property during a run session with the values stored for the same test object property within the test. 1. Checkpoint 2. All the above 3. Output Value 4. Compare the object property ANSWERE: 1 11. You will use the recording mode for an object not recognized by QuickTest. 1. Low-Level Recording Mode 2. Normal recording Mode 3. Analog Mode ANSWERE: 1 12. The statement that calls the recorded analog file is 1. RunAnalog 2. CallAnalog 3. ExecuteAnalog ANSWERE: 1 13. An action can be called by other tests or actions is 1. Call Action 2. Split Action 3. Reusable Action ANSWERE: 3 14. You can replace the page in your Active Screen tab 1. False 2. True ANSWERE: 2 15. QuickTest adds a checkpoint statement in the Expert View as 1. Check Checkpoint 2. Checkpoint ANSWERE: 1 16.A Checkpoint checks that a text string is displayed within a defined area in a Windows application is 1. Accessibility 2. Text Area 3. Standard 4. Text ANSWERE: 2 17. In ActiveX environment an “Accessibility checkpoint” is supported. 1. No 2. Yes ANSWERE: 1 18. Can we get the execution time for an action in a Test. 1. Yes 2. No ANSWERE: 1 19. Can we add external library files in QTP? 1. No 2. Yes ANSWERE: 2 20. The method used to get data from HTML Table is 1. GetData(Row,Col) 2. GetRowValue(Rowid,Colname) 3. GetCellData (Row,Col) ANSWERE: 3 21.The Command used to insert the transactions in test is, 1. StartTransaction(“Name”), EndTransaction(“Name”) 2. Services.StartTransaction "Name", Services.EndTransaction "Name" 3. "Name”, "Name” ANSWERE: 2 22. A step in which one or more values are captured at a specific point in your test and stored for the duration of the run session is 1. Output Value 2. Checkpoints 3. Active Screen ANSWERE: 1 23. QuickTest can detects an application crash and activate a defined recovery scenario to continue the run session. 1. True 2. false ANSWERE: 1 24. In Batch Test process, [...]

QTP Interview Questions


If I give some thousand tests to execute in 2 days what do u do? - Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine. What does it mean when a check point is in red color? what do u do? - A red color indicates failure. Here we analyze the cause for failure whether it is a Script Issue or Environment Issue or a Application issue. What is Object Spy in QTP? - Using the Object Spy, you can view the properties of any object in an open application. You use the Object Spy pointer to point to an object. The Object Spy displays the selected object’s hierarchy tree and its properties and values in the Properties tab of the Object Spy dialog box. What is the file extension of the code file & object repository file in QTP? - Code file extension is.vbs and object repository is.tsr Explain the concept of object repository & how QTP recognizes objects? - Object Repository: displays a tree of all objects in the current component or in the current action or entire test (depending on the object repository mode you selected). We can view or modify the test object description of any test object in the repository or to add new objects to the repository. Quicktest learns the default property values and determines in which test object class it fits. If it is not enough it adds assistive properties, one by one to the description until it has compiled the unique description. If no assistive properties are available, then it adds a special Ordinal identifier such as objects location on the page or in the source code. What are the properties you would use for identifying a browser & page when using descriptive programming? - Name would be another property apart from title that we can use. Give me an example where you have used a COM interface in your QTP project? - com interface appears in the scenario of front end and back end. for eg:if you r using oracle as back end and front end as VB or any language then for better compatibility we will go for an interface. of which COM will be one among those interfaces. Create object creates handle to the instance of the specified object so that we program can use the methods on the specified object. It is used for implementing Automation(as defined by Microsoft). Explain in brief about the QTP Automation Object Model. - Essentially all configuration and run functionality provided via the Quick Test interface is in some way represented in the Quick Test automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in Quick Test have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods. You can use the objects, methods, and properties exposed by the Quick Test automation object model, along with standard programming elements such as loops and conditional statements to design your program. Copy Rights by TestingJobsGuide [...]

Interview Questions at ADP,Hyderabad


Following are the interview question gathered from different people who attended the interview recently.Thanks to all of them who sent questions to TJG.

The opening was for QTP professional and interview digged deeply into QTP and VB Script.

  1. Frameworks at QTP?
  2. What is Object Repository?
  3. Extension for Object Repository file?
  4. Diff b/w call to existing action and call to copy of action?
  5. What is split action?
  6. Explain a critical bug you found in automation?
  7. How will you integrate QC & QTP?
  8. What is Test Plan?
  9. Diff b/w Test Plan & Test Strategy?
  10. Diff b/w QTP & Win runner?
  11. Check points and explain each of them?
  12. Why step generator?

And many more like this. According to the sources I heard, interviewer mainly concentrating on the projects done using QTP and VB Script knowledge.

Enjoy Reading!


Technical Aspects of Game Test Automation


Test automation always ahs been a lucrative way of reducing the monotonous burden on the tester. But beyond the standard incentives for test automation, sometimes automation can become almost imperative for certain kind of games. The obligation of automation is explained below: Game Speed : Sometimes, the game is to played at very high speed (say hardest level or fastest mode), which can be achieved only after a certain level of skill and experience with that particular genre of games. In this case, the tester must either spend hours in becoming master of a game, or resort to some automation technique.Game Complexity : Game play may become quite complex and the user may not be sure about the next move. This happens in planning games (ranging from Chess to Lemonade Tycoon), luck games (like card games) and in almost all multi-level games after more complex levels are reached. Again, the tester must either spend hours in becoming master of a game, or resort to some automation technique.Multiple Builds : In any commercial software – more so in games – the developer may give several builds (versions) of the game before the final market-ready build. The initial builds have several flaws (popularly called as BUGS), which are progressively removed in further builds. Every time, a similar suite of test cases has to be executed and the automation of this suite can pay rich dividends in the long run. In the current Game Testing project done by the team, some thirty-six different file versions of the game have been tested for nine consecutive builds, with minor modifications. Thus, a few extra efforts done for making automation on the first build, result in substantial saving of time and efforts later.Time/Logic Constraint : Games may need a long sequence of moves to attain completion. A classic example would be the card games like Solitaire. In such games, the tester would have to expend a lot of time to reach the end-game scenario. Secondly, the tester would have to continually apply logic for making the right moves. So his efforts are directed at playing the moves, rather than testing the game behavior. Here automation can play wonders, by handling the game moves and leaving the tester free to focus on the other aspects. (We will see the way to manage this later)Load Simulation : For multiplayer games, the tester would have to manually load the game across several platforms or use network techniques to simulate the multiplayer situation. Either way, a lot of efforts are required and still the conditions are not adequately simulated. Testing tools can provide the multi-user simulation easily. Scenario Simulation : A classical problem in game testing is when the user suspects a bug in some peculiar game scenario, but is unable to reach that particular stage easily. Suppose you believe that the transition between given levels causes a problem if some other control parameter has a particular state(Imagine that you want to see the transition from 12th to 13th level when the game character has its last life). The situation becomes also arises in case the game algorithm is already proven, and the current focus is on game experience (UI and performance verification). The tester has no desire to play the game moves, but is forced to do so, just to reach the desired stage. A testing tool, correctly programmed can provide the scenario simulation easily. Don't miss any article:Get it by E-mailCopy Rights by TestingJobsGuide [...]

Interview Questions @ CA this week


Questions gathered from interview at CA, Hyd this week.
  1. Why S/W need testing?
  2. How will you choose your test team?
  3. Testplan shouldn't contain?
  4. Extension for Object Repository in QTP? Ans: .TSR
  5. How will you communicate with client in deadline situations?
  6. QTP uses which script?
  7. QTP and QC Integration?
  8. What are list of Functional testing tools?

Will post remaining in next article. Happy Reading!

Don't miss any article:Get it by E-mail(image)

Software testing book for preparing testing interviews and learning basics of software testing [download]


I am in process to compile a list of good books on software testing. Soon I will share this list with you. But lately I am getting too many requests to share any book on software testing for preparing software testing interviews. So here is a quick post to share an online testing book I found “A Software Testing Primer” by Nick Jenkins.
Basically this book is an introduction to software testing. So those who are new to software testing field can start their preparation by reading this book. You will get basic idea of manual and automation testing.
Here is a summary of what this book is covering:
  1. What is the need of software testing?
  2. Different software development models
  3. Testing in the software development life cycle
  4. How to develop testing mindset?
  5. Regression Vs. Retesting
  6. White box Vs. Black box testing
  7. Verification and validation
  8. Alpha and beta testing
  9. Unit, Integration and System testing
  10. Acceptance testing
  11. Automation testing - Basics
  12. Testing the design
  13. Usability testing
  14. Performance testing
  15. Test planning
  16. Test estimation
  17. Test cases and elements of test cases
  18. Test tracking, Test planning and Test plan review
  19. How to manage defects and defect reports?
  20. Test metrics for testers
  21. Product release control

In all this book is a nice introduction to software testing. Author explained some key software testing concepts like Regression and Retesting difference, Alpha and beta testing etc. where many testers get confused.

Download “Testing Primer” book:To download this book Click here
What is your favorite software testing book? Also share your ‘best software testing book’ experience with our readers.

Source SoftwareTestingHelp
Don't miss any article:Get it by E-mail(image)

Interview Questions @ Infosys on this Saturday


These are the question TJG received from a source who attended for Test Engineer at Infosys,Hyd campus. According to interviewer was very cool and he got selected in that.
Total 3 rounds of interview and in that first 2 are technical followed by HR round.
Questions as follows:
  1. How you came to this testing?
  2. What is Testing?
  3. Types of Testing?
  4. What is system testing?
  5. Write test cases for yahoo messenger login?
  6. Tell me a real scenario which you ever faced?
  7. Great bug you found in your career?
  8. Problems in Communication with client?
  9. What is web testing?
  10. What should a successful Test Engineer should do?
  11. What is Bi-directional tracability matrix?

Ofcourse you will expect answers for these questions, But i don't have enough time to link them here. You can find all these answers in this site itself. Just browse through Interview Questions section.

Don't miss any article:Get it by E-mail


Interview Questions at NCR Corp,Hyd this week


Following are the interview questions asked at NCR Corp Hyderabad for an Senior Test Engineer position. One of my friend attended it and shared the questions with me.

  1. What is Static Testing?
  2. What is Dynamic Testing?
  3. Diff b/w above two?
  4. When we should go for Automation Testing and When we shouldn't?
  5. What will you do before start testing? He is asking for docs preparation!
  6. What is Tracability matrix?
  7. What is agile testing process?
  8. What is SDLC and how many models available?
  9. What is peer review and who shouldn't attend that meeting?
  10. Your short term goals?
  11. Why NCR?

Actually the requirement was for Manual Test Engineer with 3+ exp.Interviewer was a bit typical person and targetting candidate with saying no & wrong for every answer.

More over they are expecting candidate with good talent for less that 4 lacks Pa package.All positions were based on Hyderabad.

They are conducting one more drive on this sunday.Good luck!

Don't miss any article:Get it by E-mail(image)

This week interview question @ DST Global Solutions HYD


1. What is a bug?
A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result.

2.What is a test case?
Test case is set of input values, execution preconditions, expected results and executionPost conditions, developed for a particular objective or test conditions, such as to exercise a particular program path or to verify compliance with a specific requirement.

3. What is the purpose of test plan in your project?
Test plan document is prepared by the test lead, it contains the contents like introduction, objectives, test strategy, scope, test items, program modules user procedures, features to be tested features not to tested approach, pass or fail criteria, testing process, test deliverables, testing, tasks, responsibilities,resources,schedule, environmental requirements, risks & contingencies, change management procedures, plan approvals, etc all these things help a test manager understand the testing he should do & what he should follow for testing that particular project.

4. When the relationships occur between tester and developer?
Developer is the one who sends the application to the tester by doing all the necessary code in the application and sends the marshal id to the tester. The tester is the one who gives all the input/output and checks whether he is getting required output or not. A developer is the one who works on inside interfacing where as the tester is the one who works on outside interfacing

5. When testing will starts in a project?
The testing is not getting started after the coding. After release the build the testers perform the smoke test. Smoke test is the first test which is done by the testing team. This is according to the testing team. But, before the releasing of a build the developers will perform the unit testing.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail(image)

Effective Web page testing


How do we conduct effective testing in a Web page/form when we have many different fields -- textboxes, dropdown, ListBox, etc. Do we need to implement the equivalence class partitioning and boundary value analysis for all the fields? The short answer: All testing is risk-based; we cannot test everything. So we make educated assumptions. Certain fields may contain data which is not persisted in the database -- these fields might be lower-risk and perhaps do not need as much testing as others. Or the developer who coded the form may be poorly familiar with field validation and you may need to test more.The long answer? Yes, each and every field should be tested. It is the challenge of a tester to rise to the occasion and develop methodologies and tools which make him or her more efficient and more effective. Through the use of automation, it may be possible to test each field for boundary and equivalence class partitions. Perhaps by writing code which creates the HTTP POST or GET, rather than filling in each form, this coverage can be obtained. Or using data-driven testing and Selenium or Watij (Watin, Watir, etc.) it might be possible to automated the form once and loop through a series (or generate a series of data programmatically) to test boundaries and equivalence classes. Also, making use of PICT tools (pairwise, interdependent, combinatorial testing) can help you use science to narrow the field of tests you need to run to gain adequate coverage.The key to rising above other testers and QA engineers is to tackle these challenges head-on. There are many who think testers are just developers who "couldn't cut it" as developers. Unfortunately, in some cases, this is true. But the true tester will take these complicated challenges and rise above them, and will come up with creative ways to apply their engineering skills to accomplish the work at hand. And even when it's not possible to test everything, a good tester will know through logic, experience, and science when testing is complete.So the full answer is simple, but not easy. Be smart and make use of any and all tools around you. Figure out what you can accomplish in the time given, and get to it. Be scientific and think through the problem, and leverage technology to implement the solution. The goal is to have tested as much as possible in the time provided, and you will be amazed what you can do if you just take some time to figure it out.Like the guide, then subscribe by entering you mail id to get updates dailyDon't miss any article:Get it by E-mailCopy Rights by TestingJobsGuide [...]

Software performance testing: There is no 'I' in 'team'


"When everyone on the team does his job and works together to support one another the net result is almost always dramatically more desirable"

It makes more sense to think about performance testing and tuning as a team sport in which the following takes place:
  • The team works together collaboratively
  • The team is informed and involved in the decision-making process about what to test next
  • The team generates ideas about how the performance tester can help isolate performance issues using the tools that are exclusively available to him
  • The team finds out about performance issues in real time
  • The team gets to work together to help find functional errors under load
  • The members of the team who best understand the various components of the system under test get to participate in analyzing the results data in real time
  • The performance tester gets to sit next to the developer during the tune-retest-retune-retest cycle (frequently shortening that cycle from days or weeks to hours)
    Maybe I should rethink my conference

When everyone on the team does his job and works together to support one another the net result is almost always dramatically more desirable.

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail(image)

Living life as a Software Tester!


Recently I read a very interesting article on “All I Ever need to know about testing” by Lee Copeland.I was so impressed with the concept of our day to day work comparison with the software testing.I will extract only points related to software testing. As a software tester keep in mind these simple points:Share everything:If you are a experienced tester on any project then help the new developers on your project. Some testers have habit to keep the known bugs hidden till they get implement in code and then they write a big defect report on that. Don’t try to only pump your bug count, share everything with developers.Build trust:Let the developers know any bug you found in design phase. Do not log the bug repeatedly with small variations just to pump the bug count. Build trust in developer and tester relation.Don’t blame others:As a tester you should not always blame developers for the bugs. Concentrate on bug, not always on pointing that bug in front of all people. Hit the bug and its cause not the developer!Clean up your own mess:When you finish doing any test scenario then reconfigure that machine to its original configuration. The same case applies for bug report. Write a clean effective bug report. Let the developer find it easy to repro and fix it.Give credit to others for their work:Do not take others credit. If you have referred any others work, immediately give credit to that person. Do not get frustrated if you not found any bug that later has been reported by client. Do work hard, use your skill.Remember to flush Like the toilets flush all the software’s at some point. While doing performance testing remember to flush the system cache.Take a nap everyday:We need time to think, get refresh or to regenerate our energy.Some times its important to take one step back in order to get fresh insight and to find different working approach.Always work in teams, team score are always better and powerful than individuals. Like the guide, then subscribe by entering you mail id to get updates dailyDon't miss any article:Get it by E-mailCopy Rights by TestingJobsGuide [...]

Testing Metrics - Do you have examples?


Possible testing metrics are here:

• Number of test cases
• Number of tests executed
• Number of tests passed
• Number of tests failed
• Number of re-tests
• Number of Requirements tested
• Number of Defects per lines of software code or per function
• Number of Defects found in computer file types (e.g. jav, aspx, xml, xslt, html, com, doc)

Like the guide, then subscribe by entering you mail id to get updates daily
Don't miss any article:Get it by E-mail(image)