Sunday, 22 September 2013

QA job Training Toronto

QA Training Institute  stepin2it.com  presents
QA job Training with On-job Support Program
Call us on 416-743-6333   www.stepin2it.com    
• Join our Best QA Training in GTA and Toronto and get placed in the leading organization in Canada .
• Resume building and end to end support in finding work is our specialty.
• Our motto – Get you to the job market faster with ease and simplicity.
Call us on 416-743-6333
In the past year 100 of our  students have found work in Toronto and other major cities across Canada with our professional training and on – job support. Out testimonials speak about our success as a leading QA Training Provider in Toronto  .
• Every student gets On-job support till they can sustain the job.
• We are the best hands on  software testing training in GTA and Toronto. Get the skills to become a Analyst job.
• Our Profession and effective software testing training in Toronto makes us the Number 1 QA Training institute in GTA. Get Trained by the top notch professionals from the QA and Project Management Industry.
• Transform your career and get the most rewarding QA Jobs with our training and On-Job support.
• New weekend batch of   software testing training  Mississauga,Brampton, Scarborough  location on September 14- 2013 from 10.00 am to 2:00 pm.
Call us on 416-743-6333

WHY STUDENTS CHOOSE OUR TRAINING?
 Certified trainers with many years of IT experience
 Practical training sessions with live project
 Training certification assistance   ISTQB  Certified Software testing training institute Toronto
 Classroom and On-line instructor led training
 Latest and constantly updated study materials
 All latest software versions
 Tools to install and practice at home
 Instructor provides personal attention to all candidates
Call us on 416-743-6333    www.stepin2it.com

Software testing training Toronto, Testing Training Markham, Testing Training Toronto, 

Friday, 20 September 2013

software testing training and placement in Toronto

stepin2it.com  was founded with a vision in providing simplified solutions for complex Global Business requirements. Based in toronto,Canada , and its affiliated company in Toronto s, USA we are a Global “Next Generation” Information Technology Consulting, Support and Training Company working to Define, Design and Deliver world class technology enabled business solutions. At stepin2it we provide complete range of solutions and services by leveraging our domain and business expertise and strategic alliances with leading Global technology companies. stepin2it provides world class Offshore Support through our Business Center of Excellence based out of our onshore headquarters located in Toronto, CANADA . Our Knowledge Center of Excellence provides expertise in the areas of IT Staffing   and QA/Software Testing. At stepin2it we have a world class Training team providing Corporate Training to Global companies in the SAS and QA/Software Testing areas. We also provide Customer Project based Training and Placements in Toronto Canada , USA   and the Middle East to Individuals in the areas of it staffing  and QA/Software Testing.
We have expertise in  

software testing training Toronto,
software testing training in Toronto 
software testing training and placement in Toronto
online software testing training .
mobile testing training.
qa software testing training.
testing tools online training
QTP testing training.
software testing online training.
quick test professional training .


Call:416-743-6333   or visit   www.stepin2it.com      100 west more dr. Toronto Etobicoke

QTP Training Toronto,Brampton.

 Software testing training brampton
Advance QA Training Brampton

*****TRY OUR FREE DEMO CLASS*****

We are certified Software professionals with over 14 years of software industry training and placement experience. Our Strength is Placement. 90% of our students got placement in very few interviews. our FREE demo class and Start your colorful Journey…We will prove it..!!!


Advance Quick Test Professional (QTP)

# Who should attend?
This course is suitable for anyone wishing to gain more understanding of QTP tool in software testing.

#Duration: 25 hours

Course Outline

•Introduction to QTP
• Benefits of automation
• QTP testing Process
• Different types of checkpoints
• Parameterization
• Actions
• Object repository and spy
• Synchronizing a Test

• Handling exceptions using recovery scenarios

• Expert view and VB Scripting fundamentals
• VB script concepts
• Working with data tables

• Descriptive programming
• Interaction with files and database
• Functions and sub procedures
• Interacting with Microsoft Excel
• QTP Automation and test automation framework



Contact: STEPIN2IT.COM    100 WESTMORE DR   UNIT 12  ETOBICOKE   Software Solutions, Mississauga
Telephone:,416-743-6333   EMAIL  :info@stepin2it.com

We are in QA Training- Automation Training- QTP, Selenium, QC, Load Runner, Test Director, Unix, Database and Live Project
QA training and job placement assistance Toronto, QTP jobs Toronto., QTP testing training  Brampton, 

Sunday, 8 September 2013

QTP Training Scarborough, QTP training Toronto, Software Testing Training brampton and Jobs

QTP automation tool and preparation of QTP interview questions

Quick Test Professional: Interview Questions and answers.
1. What are the features and benefits of Quick Test Pro(QTP)?
1. Key word driven testing
2. Suitable for both client server and web based application
3. VB script as the script language
4. Better error handling mechanism
5. Excellent data driven testing features
2. How to handle the exceptions using recovery scenario manager in QTP?
You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario. Recovery scenario has three steps
1. Triggered Events
2. Recovery steps
3. Post Recovery Test-Run
3. What is the use of Text output value in QTP?
Output values enable to view the values that the application talks during run time. When parameterized, the values change for each iteration. Thus by creating output values, we can capture the values that the application takes for each run and output them to the data table.
4. How to use the Object spy in QTP 8.0 version?
There are two ways to Spy the objects in QTP
1) Thru file toolbar: In the File ToolBar click on the last toolbar button (an icon showing a person with hat).
2) Thru Object repository Dialog: In Objectrepository dialog click on the button “object spy…” In the Object spy Dialog click on the button showing hand symbol. The pointer now changes in to a hand symbol and we have to point out the object to spy the state of the object. If at all the object is not visible or window is minimized then hold the Ctrl button and activate the required window to and release the Ctrl button.
5. What is the file extension of the code file and object repository file in QTP?
File extension of
Per test object rep: filename.mtr
Shared Object rep: filename.tsr
Code file extension id: script.mts
6. Explain the concept of object repository and 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 Ordianl identifier such as objects location on the page or in the source code.
7. What are the properties you would use for identifying a browser and page when using descriptive programming?
“name” would be another property apart from “title” that we can use. OR
We can also use the property “micClass”.
ex: Browser(“micClass:=browser”).page(“micClass:=page”)
8. What are the different scripting languages you could use when working with QTP?
You can write scripts using following languages:
Visual Basic (VB), XML, JavaScript, Java, HTML
9. Tell some commonly used Excel VBA functions.
Common functions are:
Coloring the cell, Auto fit cell, setting navigation from link in one cell to other saving
10. Explain the keyword createobject with an example.
Creates and returns a reference to an Automation object
syntax: CreateObject(servername.typename [, location])
Arguments
servername:Required. The name of the application providing the object.
typename : Required. The type or class of the object to create.
location : Optional. The name of the network server where the object is to be created.
11. Explain in brief about the QTP Automation Object Model.
Essentially all configuration and run functionality provided via the QuickTest interface is in some way represented in the QuickTest automation object model via objects, methods, and properties. Although a one-on-one comparison cannot always be made, most dialog boxes in QuickTest 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 QuickTest automation object model, along with standard programming elements such as loops and conditional statements to design your program.
12. How to handle dynamic objects in QTP?
QTP has a unique feature called Smart Object Identification/recognition. QTP generally identifies an object by matching its test object and run time object properties. QTP may fail to recognize the dynamic objects whose properties change during run time. Hence it has an option of enabling Smart Identification, wherein it can identify the objects even if their properties changes during run time.
Check out this:
If QuickTest is unable to find any object that matches the recorded object description, or if it finds more than one object that fits the description, then QuickTest ignores the recorded description, and uses the Smart Identification mechanism to try to identify the object.
While the Smart Identification mechanism is more complex, it is more flexible, and thus, if configured logically, a Smart Identification definition can probably help QuickTest identify an object, if it is present, even when the recorded description fails.
The Smart Identification mechanism uses two types of properties:
Base filter properties – The most fundamental properties of a particular test object class; those whose values cannot be changed without changing the essence of the original object. For example, if a Web link’s tag was changed from to any other value, you could no longer call it the same object. Optional filter properties – Other properties that can help identify objects of a particular class as they are unlikely to change on a regular basis, but which can be ignored if they are no longer applicable.

 QTP Training Scarborough, QTP training Toronto, Scarborough, Selenium testing training Scarborough, Software Testing Training and Jobs placement Assistance,
QTP Training Scarborough, QTP training Toronto, Markham , Selenium testing training Scarborough,Toronto,Brampton, Software Testing Training and Jobs placement Assistance,

13. What is a Run-Time Data Table? Where can I find and view this table?
In QTP, there is data table used, which is used at runtime.
-In QTP, select the option View->Data table.
-This is basically an excel file, which is stored in the folder of the test created, its name is Default.xls by default.
14. How does Parameterization and Data-Driving relate to each other in QTP?
To data driven we have to parameterize. i.e. we have to make the constant value as parameter, so that in each interaction(cycle) it takes a value that is supplied in run-time data table. Through parameterization only we can drive a transaction (action) with different sets of data. You know running the script with the same set of data several times is not suggested, and it’s also of no use.
15. What is the difference between Call to Action and Copy Action.?
Call to Action: The changes made in Call to Action, will be reflected in the original action (from where the script is called). But where as in Copy Action , the changes made in the script ,will not effect the original script(Action)
16. Explain the concept of how QTP identifies object.
During recording qtp looks at the object and stores it as test object. For each test object QT learns a set of default properties called mandatory properties, and look at the rest of the objects to check whether this properties are enough to uniquely identify the object. During test run, QTP searches for the run time objects that matches with the test object it learned while recording.
17. Differentiate the two Object Repository Types of QTP.
Object repository is used to store all the objects in the application being tested.
Types of object repository: Per action and shared repository.
In shared repository only one centralized repository for all the tests. where as in per action for each test a separate per action repository is created.
18. What the differences are and best practical application of Object Repository?
Per Action: For Each Action, one Object Repository is created.
Shared: One Object Repository is used by entire application
19. Explain what the difference between Shared Repository and Per Action Repository
Shared Repository: Entire application uses one Object Repository , that similar to Global GUI Map file in WinRunner
Per Action: For each Action, one Object Repository is created, like GUI map file per test in WinRunner
20. Have you ever written a compiled module? If yes tell me about some of the functions that you wrote.
Sample answer (You can tell about modules you worked on. If your answer is Yes then You should expect more questions and should be able to explain those modules in later questions): I Used the functions for Capturing the dynamic data during runtime. Function used for Capturing Desktop, browser and pages.
21. Can you do more than just capture and playback?
Sample answer (Say Yes only if you worked on): I have done Dynamically capturing the objects during runtime in which no recording, no playback and no use of repository is done AT ALL.
-It was done by the windows scripting using the DOM(Document Object Model) of the windows.
22. How to do the scripting. Are there any inbuilt functions in QTP? What is the difference between them? How to handle script issues?
Yes, there’s an in-built functionality called “Step Generator” in Insert->Step->Step Generator -F7, which will generate the scripts as you enter the appropriate steps.
23. What is the difference between check point and output value?
An output value is a value captured during the test run and entered in the run-time but to a specified location.
EX:-Location in Data Table[Global sheet / local sheet]
24. How many types of Actions are there in QTP?
There are three kinds of actions:
Non-reusable action – An action that can be called only in the test with which it is stored, and can be called only once.
Reusable action – An action that can be called multiple times by the test with which it is stored (the local test) as well as by other tests.
External action – A reusable action stored with another test. External actions are read-only in the calling test, but you can choose to use a local, editable copy of the Data Table information for the external action.
25. I want to open a Notepad window without recording a test and I do not want to use System utility Run command as well. How do I do this?
You can still make the notepad open without using the record or System utility script, just by mentioning the path of the notepad “( i.e. where the notepad.exe is stored in the system) in the “Windows Applications Tab” of the “Record and Run Settings window.
QTP Training Scarborough, QTP training Toronto, Scarborough, Selenium testing training Scarborough, Software Testing Training and Jobs placement Assistance, 

SOURCE:http://www.softwaretestinghelp.com

QA training and job placement assistance, QTP & automation testing training, QTP & automation testing training Toronto, QTP course Toronto, QTP inclass/Online Training Course Toronto., QTP interview questions Call 416-743-6333 stepin2it.com

  •  QTP interview  questions
  •  
  • QTP is merely a tool that facilitates testing. The ultimate goal of QTP- or any other testing tool for that matter- is efficient and effective testing. So, make sure your testing fundamentals are solid.
  • Next undeniably is the knowledge about the QTP tool. Make sure you know all the basic information about the tool.
  • QTP predominantly relies on a tester’s programming skills to design, develop and maintain tests. That does not mean knowing all the features of the tool or VB Script are enough. The most important skill the automation tester should have is the ability for logic building. QTP tool and VB Script are simply vehicles that help you reach a solution.
  • In the recent days most interviewers are asking questions that either involve writing a script on paper or coding on a QTP installed machine. If you can code on a machine or write the code spontaneously, that’s great! If not, I suggest you to write the solution to the problem given to you in simple English statements. This will give a chance to show case your solution forming ability. Explain that to translate this solution into a program is simply a matter of referring to the help files of the programming language to find the equivalent statements.
  • In an interview, when you are writing code, please do not forget to include comments. Showcase good programming practices.
  • Before attending a QTP interview, be sure to know the version of the QTP, the add-ins that you use, the versions of all the other software you are using etc.
  • If you have not been using QTP recently but have had past experience, it helps to take a couple of hours to re-familiarize with the IDE.
The most common but crucial questions that are asked in the QTP interview. The best part of these questions is that you have time to prepare an answer in advance before even the interview begins.
  1. What are the reasons for choosing to automate your project and why did you choose QTP?
  2. What is the most challenging testing situation you faced and how did you overcome it?
  3. Did QTP prove efficient for your project? Yes or No, explain?
  4. How did you achieve reusability via QTP?
  5. Did you find anything in your project that QTP proved inefficient to perform?
  6. Under what conditions would you recommend QTP for future projects?
We suggest you spend some time with these questions and come up with answers based on your practical experience from using QTP in your respective projects.
Another important question that your interviewer would be interested to know is the statistics. For example:
  1. How many scripts did you have?
  2. How often were they executed?
  3. How many lines of code in each script?
  4. Did you use function libraries and/or shared ORs?
  5. How long to develop a script?
  6. Did the scripts need lot of maintenance? If yes, why?
Again, be sure to be prepared with the answers to these questions.
Last piece of advice, be honest and straightforward. Keep in mind that not all projects are same and not everybody follows the same methods. So we recommend that you have clear understanding of your project and exhibit the potential to learn. Nobody expects you to know everything; they only expect you to know what you do best.
Let’s move on to the technical QTP questions.

QTP Interview Questions and Answered

Top 20 Most Asked QuickTest Professional Interview Questions
1) Different types of QTP test assets and their extensions:
types of QTP test assets and their extensions
2) Technologies supported by QTP:
Web, Java (Core and Advanced), .Net, WPF, SAP, Oracle, Siebel, PeopleSoft, Delphi, Power Builder, Stingray 1, Terminal Emulator, Flex, Web Services, Windows Mobile, VisualAge Smalltalk, Silverlight and mainframe terminal emulator
3) Does QTP run in any environment?
No, QTP works only in the windows environment.
4) Explain the views in the QTP GUI?
Keyword view: This view is a tabular representation of all the objects and the actions that are performed on them. Every row in the table is a step performed on the AUT and can be modified. Some of the most common columns displayed are: item, operation, value and documentation.
Expert view: As the name indicates, this view is for more technical users who would want to tweak the source code as per their requirements.
5) What is QTP’s model for test creation?
a) Determine testing needs – Define testing environment, Analyse your application and plan actions
b) Set up repositories – Local or Shared OR
c) Define function libraries
d) Generate test steps – Add steps, Add checkpoints
e) Data drive your tests
f) Run the tests
6) What are the different kinds of test steps?
5 types of steps:
- Test Object ( Performs actions on a TO)
- Functions
- Utility (Steps to control run session. Eg: Reporter.report)
- Comment
- Programming logic (Loop, conditions…etc)
7) What are the different ways to invoke an application using QTP?
a) SystemUtil.Run
SystemUtil.Run ( FileName, Parameters, Path, Operation )
Example: SystemUtil.Run(“iexplorer.exe”,http://www.google.com)
SystemUtil.Run(“test.txt”, “”,”C:\”,”1”)
b) InvokeApplication
Example: InvokeApplication “C:\Program Files\Internet Explorer\IEXPLORE.EXE http://www.google.com”


c) Creating a shell object using VB Script
Example: Create a “WScript.shell” object.
Dim testshell
Set testshell= CreateObject (“Wscript.shell”)
testshell.run “%windir%\notepad “
8) What are the different recording modes and how do they work?
QTP provides 3 modes of recording:
  • Normal Recording mode – The default recording method is always the normal mode. This method uses the model of Test Objects and Runtime objects to learn and act on the AUT.
  • Analog recording mode – records the exact mouse and key strokes that the user performs in relation to either the screen or AUT window.  The steps that are recorded using this method cannot be edited.
    The way this usually gets represented in a code is:
    Window/app.RunAnalog “Track1”
    One scenario in which this type of recording can be used is when we are trying
    to capture a signature.
  • Low Level recording mode – This mode records the co-ordinates in the application where the operation is performed, irrespective of whether QTP recognizes the specific Object or Operation.
9) Which recording modes need more memory?
Analog and Low-level recording modes
10) Is it possible to switch between recording modes during a test creation?
Yes, in the middle of recording, we can switch to Analog/Low-level mode, finish the task required and go back to normal recording. The switch to Analog mode is available only during recording and not during editing
11) Does Low level recording capture mouse movements?
No. Mouse movements are not captured.
12) How does QTP identify an object?
QTP has a predetermined set of properties that it learns/stores for every class of object it identifies. There are 3 aspects to this:
  • Mandatory properties: This is the list of properties for a certain class that QTP always stores. We could say that this is the object description. It also checks this in conjunction with the parent object to see if the description is sufficient to identify the object uniquely.
  • Assistive properties: In case the description of mandatory properties is insufficient to identify the Object a set of non-mandatory properties will be added to the description one after the other until there is enough data to identify the object.
  • Ordinal Identifier: If the assistive properties also do not result in unique identification of an object a special ordinal identifier is added by QTP, such as the object’s location on the page or in the source code.
13) What is Smart identification?
If the recorded description does not enable QTP to identify a specific object then QTP uses “Smart identification” mechanism.  It uses the following additional properties to identify the object
a) Base Filter Properties (primary) – The set of properties that cannot be changed without changing the object type
b) Optional Filter Properties (secondary) – additional properties that help identify the object uniquely.
14) What is Object Spy?
Object Spy is an extremely helpful tool that QTP has to view the properties and operations of an object in the AUT. It shows all the properties of the object and the corresponding values. It also shows the object hierarchy. It also has a provision that lets the users add a certain object to the OR.
15) What is an object repository?
OR is like a warehouse where all the objects in a test are stored. OR has the list of Objects that QTP learned during the record process and the class to which they belong. It stores the set of properties that uniquely identifies the Object (description) and also names the object for the sake of identification in our test, based on its most prominent feature.
16) What are the two types of repositories available, explain them?
Local and shared repository – these are the two kinds of available repositories.
Every action by default has a local repository of its own and has all the objects that are used within it.
Alternately, the tester can have a common repository for multiple actions so that all of them can share the objects that it contains. The common repository is called a shared OR.
17) An action has both shared and local OR associated to it and both have the same object in them. In the test which one will be considered?
If a local OR and Shared OR have an object with the same name, the action will consider the object in its local OR.
18) Can an action have 2 shared object repositories associated with them? In that case, if two of them contain the same object, which one will be considered?
There can be more than one Shared OR’s associated to the same action. If Shared OR1 and Shared OR2 have one object named OBJ1 each and if the action calls for OBJ1 then the order in which the shared ORs were associated will be considered. That means, if Shared OR1 was first associated then the OBJ1 from Shared OR1 will be taken into account.
19) Can the user toggle between using Local OR and shared OR for the same action?
Yes, it is possible to switch between one or the other types of ORs at any time. To do so, the menu option is Test->Settings->Resources and choosing the options accordingly.
20) Are Shared ORs read only?
By default, shared ORs open as read only. To open them in order to edit them you will have to open them from Object Repository Manager.
“ORM->File->Enable Editing”


QA training and job placement assistance, QTP & automation testing training, QTP & automation testing training Toronto, QTP course Toronto, QTP inclass/Online Training Course Toronto., 

Software Testing Training toronto Interview Answers

  1. What is the MAIN benefit of designing tests early in the life cycle? 
Designing tests early in the life cycle can prevent defects from being introduced into the code.

Software Testing Training Toronto  Interview Answers
  1. What is risk-based testing?
Risk-based testing is the term used for an approach to creating a test strategy that is based on prioritizing tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level. Tests to address each risk are then specified, starting with the highest risk first.

Software Testing Training Brampton,Mississauga    stepin2it.com   call 416-743-6333

  1. What is the KEY difference between preventative and reactive approaches to testing?
Preventative tests are designed early whereas reactive tests are designed after the software has been produced
  1. What is the purpose of exit criteria? 
An exit criterion defines when a test level is complete.
  1. What determines the level of risk? 
The likelihood of an adverse event and the impact of the event determine the level of risk.
  1. When is used Decision table testing? 
Decision table testing is used for testing systems for which the specification takes the form of rules or cause-effect combinations. In a decision table the inputs are listed in a column, with the outputs in the same column but below the inputs. The remainder of the table explores combinations of inputs to define the outputs produced.
  1. What is beta testing?
Beta testing is testing that is performed by potential customers at their own locations.
  1. Which is a benefit of test independence?
It avoids author bias in defining effective tests.
  1. What is component testing?
Component testing, also known as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are able to be tested separately. Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system.
  1. What is functional system testing?
Testing the end to end functionality of the system as a whole.
  1. What are the benefits of Independent Testing
Independent testers are unbiased.
  1. In a reactive approach to testing when would you expect the bulk of the test design work to be implemented?
After the software or system has been produced.
  1. When should configuration management procedures be implemented?
During test planning.
  1. What are the white-box testing techniques?
White-box testing techniques use the internal structure of the software to derive test cases. They are commonly called 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software works.
  1. How much testing is enough?
It depends on the risks, contract and special requirements.
  1. What is exploratory testing?
Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used. The test design and test execution activities are performed in parallel typically without formally documenting the test conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not be used. Some notes will be written during the exploratory-testing session, so that a report can be produced afterwards.
  1. What is failure?
Failure is the deviation from expected result to actual result

qa training and placement assistance, QA training and job placement assistance Toronto, QA training Brampton and placement assistance,

37. What's the difference between System testing and Acceptance testing?
Acceptance testing checks the system against the "Requirements." It is similar to System testing in that the whole system is checked but the important difference is the change in focus:

System testing checks that the system that was specified has been delivered. Acceptance testing checks that the system will deliver what was requested. The customer should always do Acceptance testing and not the developer.

qa training and placement assistance, QA training and job placement assistance Toronto, QA training Brampton and placement assistance,

The customer knows what is required from the system to achieve value in the business and is the only person qualified to make that judgement. This testing is more about ensuring that the software is delivered as defined by the customer. It's like getting a green light from the customer that the software meets expectations and is ready to be used.
38. Can you explain regression testing and confirmation testing?
Regression testing is used for regression defects. Regression defects are defects occur when the functionality which was once working normally has stopped working. This is probably because of changes made in the program or the environment. To uncover such kind of defect regression testing is conducted.

The following figure shows the difference between regression and confirmation testing.

Software Testing Image

If we fix a defect in an existing application we use confirmation testing to test if the defect is removed. It's very possible because of this defect or changes to the application that other sections of the application are affected. So to ensure that no other section is affected we can use regression testing to confirm this.


Source :http://www.indiabix.com

Testing Training Markham, Testing Training Mississauga, Testing Training Scarborough, Testing Training Toronto, Software Testing Training Ottawa, software testing training Brampton,

Testing Training Markham, Testing Training Mississauga, Testing Training Scarborough, Testing Training Toronto, Software Testing Training Ottawa, software testing training Toronto, 


Call stepin2it.com  call 416-743-6333       

31. What kind of input do we need from the end user to begin proper testing?
The product has to be used by the user. He is the most important person as he has more interest than anyone else in the project.

Software Testing Image

From the user we need the following data:

  • The first thing we need is the acceptance test plan from the end user. The acceptance test defines the entire test which the product has to pass so that it can go into production.
  • We also need the requirement document from the customer. In normal scenarios the customer never writes a formal document until he is really sure of his requirements. But at some point the customer should sign saying yes this is what he wants.
  • The customer should also define the risky sections of the project. For instance, in a normal accounting project if a voucher entry screen does not work that will stop the accounting functionality completely. But if reports are not derived the accounting department can use it for some time. The customer is the right person to say which section will affect him the most. With this feedback the testers can prepare a proper test plan for those areas and test it thoroughly.
  • The customer should also provide proper data for testing. Feeding proper data during testing is very important. In many scenarios testers key in wrong data and expect results which are of no interest to the customer.
32. Can you explain the workbench concept?
In order to understand testing methodology we need to understand the workbench concept. A Workbench is a way of documenting how a specific activity has to be performed. A workbench is referred to as phases, steps, and tasks as shown in the following figure.

Software Testing Image

There are five tasks for every workbench:

  • Input: Every task needs some defined input and entrance criteria. So for every workbench we need defined inputs. Input forms the first steps of the workbench.
  • Execute: This is the main task of the workbench which will transform the input into the expected output.
  • Check: Check steps assure that the output after execution meets the desired result.
  • Production output: If the check is right the production output forms the exit criteria of the workbench.
  • Rework: During the check step if the output is not as desired then we need to again start from the execute step.

Software Testing Image
33. Can you explain the concept of defect cascading?
Defect cascading is a defect which is caused by another defect. One defect triggers the other defect. For instance, in the accounting application shown here there is a defect which leads to negative taxation. So the negative taxation defect affects the ledger which in turn affects four other modules.

Software Testing Image
34. Can you explain cohabiting software?
When we install the application at the end client it is very possible that on the same PC other applications also exist. It is also very possible that those applications share common DLLs, resources etc., with your application. There is a huge chance in such situations that your changes can affect the cohabiting software. So the best practice is after you install your application or after any changes, tell other application owners to run a test cycle on their application.

Software Testing Image
35. What is the difference between pilot and beta testing?
The difference between pilot and beta testing is that pilot testing is nothing but actually using the product (limited to some users) and in beta testing we do not input real data, but it's installed at the end customer to validate if the product can be used in production.

Software Testing Image
36. What are the different strategies for rollout to end users?
There are four major ways of rolling out any project:

Software Testing Image


  • Pilot: The actual production system is installed at a single or limited number of users. Pilot basically means that the product is actually rolled out to limited users for real work.
  • Gradual Implementation: In this implementation we ship the entire product to the limited users or all users at the customer end. Here, the developers get instant feedback from the recipients which allow them to make changes before the product is available. But the downside is that developers and testers maintain more than one version at one time.
  • Phased Implementation: In this implementation the product is rolled out to all users in incrementally. That means each successive rollout has some added functionality. So as new functionality comes in, new installations occur and the customer tests them progressively. The benefit of this kind of rollout is that customers can start using the functionality and provide valuable feedback progressively. The only issue here is that with each rollout and added functionality the integration becomes more complicated.
  • Parallel Implementation: In these types of rollouts the existing application is run side by side with the new application. If there are any issues with the new application we again move back to the old application. One of the biggest problems with parallel implementation is we need extra hardware, software, and resources. 
SOURCE: http://www.indiabix.com

Software Testing Training Toronto,Software Testing Training Mississauga,Software Testing Training Markham, Software Software Testing training Toronto and placement assistance,

Software Testing Training Toronto,Software Testing Training Mississauga,Software Testing Training Markham, Software Software Testing training Toronto  and placement assistance, software testing training Toronto.


STEPIN2IT.COM    CALL 416-743-6333   

25. What is the difference between latent and masked defects?
A latent defect is an existing defect that has not yet caused a failure because the sets of conditions were never met.

A masked defect is an existing defect that hasn't yet caused a failure just because another defect has prevented that part of the code from being executed.

Testing Training Toronto, Testing Training Mississauga, Testing Training Markham, Software Testing training Toronto  and placement assistance, software testing training Toronto, 

26. Can you explain calibration?
It includes tracing the accuracy of the devices used in the production, development and testing. Devices used must be maintained and calibrated to ensure that it is working in good order.
27. What's the difference between alpha and beta testing?
Software Testing Image

Alpha and beta testing has different meanings to different people. Alpha testing is the acceptance testing done at the development site. Some organizations have a different visualization of alpha testing. They consider alpha testing as testing which is conducted on early, unstable versions of software. On the contrary beta testing is acceptance testing conducted at the customer end.

In short, the difference between beta testing and alpha testing is the location where the tests are done.
28. How does testing affect risk?
A risk is a condition that can result in a loss. Risk can only be controlled in different scenarios but not eliminated completely. A defect normally converts to a risk.

Software Testing Image
29. What is coverage and what are the different types of coverage techniques?
Coverage is a measurement used in software testing to describe the degree to which the source code is tested. There are three basic types of coverage techniques as shown in the following figure:

Software Testing Image


  • Statement coverage: This coverage ensures that each line of source code has been executed and tested.
  • Decision coverage: This coverage ensures that every decision (true/false) in the source code has been executed and tested.
  • Path coverage: In this coverage we ensure that every possible route through a given part of code is executed and tested.
30. A defect which could have been removed during the initial stage is removed in a later stage. How does this affect cost?
If a defect is known at the initial stage then it should be removed during that stage/phase itself rather than at some later stage. It's a recorded fact that if a defect is delayed for later phases it proves more costly. The following figure shows how a defect is costly as the phases move forward. A defect if identified and removed during the requirement and design phase is the most cost effective, while a defect removed during maintenance is 20 times costlier than during the requirement and design phases.

Software Testing Image

For instance, if a defect is identified during requirement and design we only need to change the documentation, but if identified during the maintenance phase we not only need to fix the defect, but also change our test plans, do regression testing, and change all documentation. This is why a defect should be identified/removed in earlier phases and the testing department should be involved right from the requirement phase and not after the execution phase.

Source:http://www.indiabix.com/

QA training Brampton and placement assistance, QA training Brampton and placement Mississauga, QA training Brampton and placement Mississauga, QA Training Canada, QTP jobs Toronto.,

19. Which test cases are written first: white boxes or black boxes?
Normally black box test cases are written first and white box test cases later. In order to write black box test cases we need the requirement document and, design or project plan. All these documents are easily available at the initial start of the project. White box test cases cannot be started in the initial phase of the project because they need more architecture clarity which is not available at the start of the project. So normally white box test cases are written after black box test cases are written.

Black box test cases do not require system understanding but white box testing needs more structural understanding. And structural understanding is clearer i00n the later part of project, i.e., while executing or designing. For black box testing you need to only analyze from the functional perspective which is easily available from a simple requirement document.

Software Testing Image
20. Explain Unit Testing, Integration Tests, System Testing and Acceptance Testing?
Unit testing - Testing performed on a single, stand-alone module or unit of code.

Integration Tests - Testing performed on groups of modules to ensure that data and control are passed properly between modules.

System testing - Testing a predetermined combination of tests that, when executed successfully meets requirements.

Acceptance testing - Testing to ensure that the system meets the needs of the organization and the end user or customer (i.e., validates that the right system was built).
21. What is a test log?
The IEEE Std. 829-1998 defines a test log as a chronological record of relevant details about the execution of test cases. It's a detailed view of activity and events given in chronological manner.

The following figure shows a test log and is followed by a sample test log.

Software Testing Image
22. Can you explain requirement traceability and its importance?
In most organizations testing only starts after the execution/coding phase of the project. But if the organization wants to really benefit from testing, then testers should get involved right from the requirement phase.

If the tester gets involved right from the requirement phase then requirement traceability is one of the important reports that can detail what kind of test coverage the test cases have.
23. What does entry and exit criteria mean in a project?
Entry and exit criteria are a must for the success of any project. If you do not know where to start and where to finish then your goals are not clear. By defining exit and entry criteria you define your boundaries.

For instance, you can define entry criteria that the customer should provide the requirement document or acceptance plan. If this entry criteria is not met then you will not start the project. On the other end, you can also define exit criteria for your project. For instance, one of the common exit criteria in projects is that the customer has successfully executed the acceptance test plan.

Software Testing Image
24. What is the difference between verification and validation?
Verification is a review without actually executing the process while validation is checking the product with actual execution. For instance, code review and syntax check is verification while actually running the product and checking the results is validation.

QA training Brampton and placement assistance, QA training Brampton and placement Mississauga, QA training Brampton and placement Mississauga, QA Training Canada, QTP jobs Toronto., 
source :http://www.indiabix.com

Testing Training Scarborough, Testing Training Toronto,

13. What group of teams can do software testing?
When it comes to testing everyone in the world can be involved right from the developer to the project manager to the customer. But below are different types of team groups which can be present in a project.

  • Isolated test team
  • Outsource - we can hire external testing resources and do testing for our project.
  • Inside test team
  • Developers as testers
  • QA/QC team.
14. What impact ratings have you used in your projects?
Normally, the impact ratings for defects are classified into three types:

Software Testing Image


  • Minor: Very low impact but does not affect operations on a large scale.
  • Major: Affects operations on a very large scale.
  • Critical: Brings the system to a halt and stops the show.
15. Does an increase in testing always improve the project?
No an increase in testing does not always mean improvement of the product, company, or project. In real test scenarios only 20% of test plans are critical from a business angle. Running those critical test plans will assure that the testing is properly done. The following graph explains the impact of under testing and over testing. If you under test a system the number of defects will increase, but if you over test a system your cost of testing will increase. Even if your defects come down your cost of testing has gone up.
16. What's the relationship between environment reality and test phases?
Environment reality becomes more important as test phases start moving ahead. For instance, during unit testing you need the environment to be partly real, but at the acceptance phase you should have a 100% real environment, or we can say it should be the actual real environment. The following graph shows how with every phase the environment reality should also increase and finally during acceptance it should be 100% real.

Software Testing Image
17. What are different types of verifications?
Verification is static type of s/w testing. It means code is not executed. The product is evaluated by going through the code. Types of verification are:


  1. Walkthrough: Walkthroughs are informal, initiated by the author of the s/w product to a colleague for assistance in locating defects or suggestions for improvements. They are usually unplanned. Author explains the product; colleague comes out with observations and author notes down relevant points and takes corrective actions.
  2. Inspection: Inspection is a thorough word-by-word checking of a software product with the intention of Locating defects, Confirming traceability of relevant requirements etc.
18. How do test documents in a project span across the software development lifecycle?
The following figure shows pictorially how test documents span across the software development lifecycle. The following discusses the specific testing documents in the lifecycle:

Software Testing Image


  • Central/Project test plan: This is the main test plan which outlines the complete test strategy of the software project. This document should be prepared before the start of the project and is used until the end of the software development lifecycle.
  • Acceptance test plan: This test plan is normally prepared with the end customer. This document commences during the requirement phase and is completed at final delivery.
  • System test plan: This test plan starts during the design phase and proceeds until the end of the project.
  • Integration and unit test plan: Both of these test plans start during the execution phase and continue until the final delivery. 
 Testing Training Scarborough, Testing Training Toronto, Testing Training Markham, Struts Training, Software Testing training Toronto  and placement assistance,

source :http://www.indiabix.com

Software Testing training Basics - Software Testing training toronto Interview Questions and Answers

7. What is configuration management?
Configuration management is the detailed recording and updating of information for hardware and software components. When we say components we not only mean source code. It can be tracking of changes for software documents such as requirement, design, test cases, etc.

When changes are done in adhoc and in an uncontrolled manner chaotic situations can arise and more defects injected. So whenever changes are done it should be done in a controlled fashion and with proper versioning. At any moment of time we should be able to revert back to the old version. The main intention of configuration management is to track our changes if we have issues with the current system. Configuration management is done using baselines.
8. How does a coverage tool work?
While doing testing on the actual product, the code coverage testing tool is run simultaneously. While the testing is going on, the code coverage tool monitors the executed statements of the source code. When the final testing is completed we get a complete report of the pending statements and also get the coverage percentage.

Software Testing Image
9. Which is the best testing model?
In real projects, tailored models are proven to be the best, because they share features from The Waterfall, Iterative, Evolutionary models, etc., and can fit into real life time projects. Tailored models are most productive and beneficial for many organizations. If it's a pure testing project, then the V model is the best.
10. What is the difference between a defect and a failure?
When a defect reaches the end customer it is called a failure and if the defect is detected internally and resolved it's called a defect.

Software Testing Image
11. Should testing be done only after the build and execution phases are complete?
In traditional testing methodology testing is always done after the build and execution phases.

But that's a wrong way of thinking because the earlier we catch a defect, the more cost effective it is. For instance, fixing a defect in maintenance is ten times more costly than fixing it during execution.

In the requirement phase we can verify if the requirements are met according to the customer needs. During design we can check whether the design document covers all the requirements. In this stage we can also generate rough functional data. We can also review the design document from the architecture and the correctness perspectives. In the build and execution phase we can execute unit test cases and generate structural and functional data. And finally comes the testing phase done in the traditional way. i.e., run the system test cases and see if the system works according to the requirements. During installation we need to see if the system is compatible with the software. Finally, during the maintenance phase when any fixes are made we can retest the fixes and follow the regression testing.

Therefore, Testing should occur in conjunction with each phase of the software development.
12. Are there more defects in the design phase or in the coding phase?
The design phase is more error prone than the execution phase. One of the most frequent defects which occur during design is that the product does not cover the complete requirements of the customer. Second is wrong or bad architecture and technical decisions make the next phase, execution, more prone to defects. Because the design phase drives the execution phase it's the most critical phase to test. The testing of the design phase can be done by good review. On average, 60% of defects occur during design and 40% during the execution phase.


Selenium Training course Toronto with job placement assistance.Selenium Training course Mississauga with job placement assistance., Software testing training Brampton, Software Testing Image

Software Testing training toronto Interview Questions and Answers

Stepin2it.COM        Call 416-743-6333  for software testing training Toronto, Brampton, Scarborough,Mississauga.  
Software Testing training Toronto Basics
1. Can you explain the PDCA cycle and where testing fits in?
Software testing is an important part of the software development process. In normal software development there are four important steps, also referred to, in short, as the PDCA (Plan, Do, Check, Act) cycle.
Software Testing Image
Let's review the four steps in detail.

  1. Plan: Define the goal and the plan for achieving that goal.
  2. Do/Execute: Depending on the plan strategy decided during the plan stage we do execution accordingly in this phase.
  3. Check: Check/Test to ensure that we are moving according to plan and are getting the desired results.
  4. Act: During the check cycle, if any issues are there, then we take appropriate action accordingly and revise our plan again.

So developers and other stakeholders of the project do the "planning and building," while testers do the check part of the cycle. Therefore, software testing is done in check part of the PDCA cyle.
2. What is the difference between white box, black box, and gray box testing?
Black box testing is a testing strategy based solely on requirements and specifications. Black box testing requires no knowledge of internal paths, structures, or implementation of the software being tested.

White box testing is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.

There is one more type of testing called gray box testing. In this we look into the "box" being tested just long enough to understand how it has been implemented. Then we close up the box and use our knowledge to choose more effective black box tests.

Software Testing Image

The above figure shows how both types of testers view an accounting application during testing. Black box testers view the basic accounting application. While during white box testing the tester knows the internal structure of the application. In most scenarios white box testing is done by developers as they know the internals of the application. In black box testing we check the overall functionality of the application while in white box testing we do code reviews, view the architecture, remove bad code practices, and do component level testing.
3. Can you explain usability testing?
Usability testing is a testing methodology where the end customer is asked to use the software to see if the product is easy to use, to see the customer's perception and task time. The best way to finalize the customer point of view for usability is by using prototype or mock-up software during the initial stages. By giving the customer the prototype before the development start-up we confirm that we are not missing anything from the user point of view.

Software Testing Image
4. What are the categories of defects?
There are three main categories of defects:
Software Testing Image

  1. Wrong: The requirements have been implemented incorrectly. This defect is a variance from the given specification.
  2. Missing: There was a requirement given by the customer and it was not done. This is a variance from the specifications, an indication that a specification was not implemented, or a requirement of the customer was not noted properly.
  3. Extra: A requirement incorporated into the product that was not given by the end customer. This is always a variance from the specification, but may be an attribute desired by the user of the product. However, it is considered a defect because it's a variance from the existing requirements.
5. How do you define a testing policy?
The following are the important steps used to define a testing policy in general. But it can change according to your organization. Let's discuss in detail the steps of implementing a testing policy in an organization.

Software Testing Image


  • Definition: The first step any organization needs to do is define one unique definition for testing within the organization so that everyone is of the same mindset.
  • How to achieve: How are we going to achieve our objective? Is there going to be a testing committee, will there be compulsory test plans which need to be executed, etc?.
  • Evaluate: After testing is implemented in a project how do we evaluate it? Are we going to derive metrics of defects per phase, per programmer, etc. Finally, it's important to let everyone know how testing has added value to the project?.
  • Standards: Finally, what are the standards we want to achieve by testing? For instance, we can say that more than 20 defects per KLOC will be considered below standard and code review should be done for it.
6. On what basis is the acceptance plan prepared?
In any project the acceptance document is normally prepared using the following inputs. This can vary from company to company and from project to project.

  1. Requirement document: This document specifies what exactly is needed in the project from the customers perspective.
  2. Input from customer: This can be discussions, informal talks, emails, etc.
  3. Project plan: The project plan prepared by the project manager also serves as good input to finalize your acceptance test.

The following diagram shows the most common inputs used to prepare acceptance test plans.

Software Testing Image




Source :http://www.indiabix.com

Friday, 6 September 2013

Software testing training Toronto ,Brampton ,Markham. Mississauga,Scarborough

We specialize in providing best hand on professional software testing  training  Toronto services in Software QA Testing, QTP, Manual Testing, Performance Testing, Mobile Apps Testing, LoadRunner, and Automation Testing with latest updates.

Our instructors have 12 years of experience maintaining in the area of software testing.

We  provide live projects, which includes E Commerce Project, Baking Project, Health Care Project, , and many other domains.
Benefits of Software testing  training courses :
Software testing training Toronto ,Brampton ,Markham. Mississauga,Scarborough.
- Enrol once and enjoy a lifetime  access to all our live classes and materials.
- onsite/online  , instructor led class available .-
- Real time project work sessions on various domains.
- Walk into your next interview with confident as you attend our unlimited mock interview sessions.
- Help with Resume preparation by our experts.
- Recruiter driven placement service.100% job placment assiatnace
- course material is  built based on professional standards and employer insights
- Instructors are  ISTQB  Certified Experts in SOFTWARE TESTING  field and they bring years of industry experience into the training classes.
CALL 416-743-6333 EMAIL US :info@stepin2it.ca   www.stepin2it.com   www.stepin2it.com

QA training Toronto

1)Are you prepared for job market challenges?

2) Not receiving enough calls?

3) Struggling to find a job in today's job market?

The answer to these problems is to self assess your skills and seek professional help in retraining and upgrading your skills to make them more relevant to the current job market. Train for a Career not just a job and we can help.

STEPIN2IT is a Toronto Based premier training organization offering Training Programs across different genres in IT Industry. Our unique approach to training has helped many a student to improve their skill set and successfully find a job in today's tough market conditions. If you are interested in maximizing your potential and differentiating yourself from the rest of your competition, read further.

Programs are designed keeping in mind various levels of programming knowledge and skills. Beginner and Advanced programs available.

SKILLS UPGRADE Programs Offered:

* Software Testing Program -- 35 Hours offered on Weekdays/Weekends

For a list of all courses we offer and recruitment assistance, please contact us.

Call us: 416-743-6333 or visit us on www.stepin2it.com

Why choose US:

ü Mentorship & facilitation from Industry professionals

ü Small class sizes

ü Quality instructors (Certified & Experienced Professionals)

Guaranteed competence through hands on training approach

ü Cost-effective Training

ü FREE Reading Material

ü Access to network of Recruiters & Clients

ü 100% job assistance to all students through our sister recruiting company

ü Job Help & Support

ü Lab Access



WE DO PROVIDE ONLINE CLASSES.


Software testing training Toronto, software testing jobs Toronto, qa training Toronto, sqa training Toronto, QA TRNG, Testing TRNG Toronto, Testing Training Toronto, Testing Training Markham, Testing Training Scarborough, Testing Training Mississauga, QTP Training Toronto, QTP Training Mississauga, QTP Training Scarborough, Loadrunner Training Toronto, Loadrunner Training Mississauga, Loadrunner Training Scarborough, Selenium Training Toronto, Selenium

Thursday, 5 September 2013

Manual testing toronto interview questions

Hi, I found this document to be helpful while planning for manual testing interview.Personal Question

1.    How you want to see yourself after 3 years?
I would be looking at a senior member in the organization where i could take some crucial decision and also leading a team of testers.

2.    What is your life dream?
To be a good manager for a team of young testers.

3.    Tell about your Positives and negatives?
My positives are group work and adjusting mentality. My negatives are difficulty in saying a 'no'.

4.    In what way you say that this work given to you will be done better than others?
My ability for team work, better understanding, and client coordination will give a better out put.

5.    When you realize for a relentless fault that you have done that will cause a major problem how you will react?
I will owe it up and explain to my seniors about how i did the mistake and apologize for the same. Then will find ways by which i can solve the issue.

6.    How will be your Problem management in absence of your immediate senior?
I will talk to my team members and take a collective decision and talk to senior over phone and tell him about the team decision and ask him for his advice and proceed as per his instructions.

7.    Tell me about your very good and very bad experience?
My good experience was after SIT a few bugs were not rectified and send to client the developers took the responsibility for the bugs. When the same issue was raised by the client the developers said that they had rectified it. Since the issue was raised by the client it     directly came top the quality dept from our top management and since i had screen shoots and explained the situation to my seniors before sending the release i was not affected by it.

8.    When you are forced to do the work that is not coming under your responsibility what will you do?
It will basically depend on the scope of the project. If it is not there in the scope will tell them it is not in our project scope. But if we happen to see that the client is a very important for the organization will try to put in some extra effort and do the work for the client.


Software testing training Toronto,Software testing training Brampton,Software testing training Mississauga,
Software testing training Markham,Software testing training Scarborough,
QA Training Toronto,QA Training Brampton,QA Training Mississauga, QA Training Markham,QA Training Scarborough,QA Training Canada.









Technical Questions

1.    What is Software Testing?
Software testing is a testing to make a product bug free. Testing involves operation of a system or application under controlled conditions and evaluating the results. The controlled conditions should include both normal and abnormal conditions.

2.    What is the Purpose of Testing?
To give a product to the client that is bug free and working up to the expectation of the client as his requirement.

3.    What types of testing do testers perform?
Unit Testing, Integration Testing, SIT, UAT, Black Box and White Box.

4.    What is the Outcome of Testing?
A bug free product as per the expectation of the client.

5.    What kind of testing have you done?
Unit Testing and SIT.

6.    What is the need for testing?
To give a product to the client that is bug free and working up to the expectation of the client as his requirement.

7.    What are the entry criteria for Functionality and Performance testing?
Functionality Testing: All the relevant documents should be prepared (Test condition, Cases) and signed off by the client. The testing environment should be freeze.
Performance testing: The application should be stable and SIT should have been done.

9.    What is test metrics?
Test Metrics is a mechanism to know the effectiveness of the testing that can be measured quantitatively. It is a feedback mechanism to improve the Testing Process that is followed currently.
Test metrics should cover basically 3 things:
a.    Test coverage.
b.    Time for one test cycle.
c.    Convergence of testing.

10.    Why do you go for White box testing, when Black box testing is available?
To check the internal logic and to cover all basis path and loop testing.

11.    What are the entry criteria for Automation testing?
The entry criteria is that the application should be stable.

12.    When to start and Stop Testing?
Testing can start once the coding is completed and application is stable or a part of the module coding is completed. Testing can end once all the bugs raised by the tester is rectified or differed for future enhancement.



13.    What is Quality?
A product that is fit to use. Quality means getting things right at the first time when it is done.

14.    What is Baseline document, Can you say any two?
These documents are used for testing and developing they are Functional Specification and Business Requirement.

15.    What is verification?
The process of evaluating a system or component to determine whether the products of the given development phase satisfy the conditions imposed at the start of that phase. [IEEE] [Did we develop the right product?]

16.    What is validation?
Determination of the correctness of the products of software development with respect to the user needs and requirements. [Did we develop the product right?]

17.    What is quality assurance?
A planned and systematic set of activities to ensure that variances in processes are clearly identified, assessed and improving defined processes for fulfilling the requirements of customers and product or service makers.

A planned and systematic pattern of all actions necessary to provide adequate confidence that the product optimally fulfils customer's expectations.

A planned and systematic set of activities to ensure that requirements are clearly established and the defined process complies with these requirements.

18.    What is quality control?
Quality control is a process by which actually helps us in delivering a product that is bug free and maintains some standards

19.    What are SDLC and TLC?
SDCL is Software Development Life Cycle and TLC is Testing Life Cycle

20.    What are the Qualities of a Tester?
A tester should have a good logical understanding of the application and his job is to see ways by which he can find errors in the system. He should also give some good constructive ideas to the development team to develop a good product.

21.    When to start and Stop Testing?
Testing can start once the coding is completed and application is stable or a part of the module coding is completed. Testing     can end once all the bugs raised by the tester is rectified or differed for future enhancement.

22.    What are the various levels of testing?
Unit Testing
Integration Testing
SIT
UAT


23.    What are the types of testing you know and you experienced?
Unit Testing
Integration Testing
SIT

24.    What exactly is Heuristic checklist approach for unit testing?
It is one of the techniques used in usability testing

25.    After completing testing, what would you deliver to the client?
Test Closure Documents like Test Case, Test Conditions, Traceability Matrix, Defect Report, Test Summary Report, Test Data and Down Time Report.

26.    What is a Test Bed?
It is set of data we input when we get a blank database for starting the testing.

27.    What is a Data Guidelines?
Guidelines which are the inputs for preparing the data.

28.    Why do you go for Test Bed?
When we get a empty database for testing it will not be possible for us to start testing so we need to input some initial data so that we can start the testing (so that we do not get data set up problems).

29.    What is Severity and Priority and who will decide what?
Severity is to tell how whether the bug is Critical, Medium, or Low. If it is critical it is a show stopper if it is medium it has some functional problem but can proceed if it is low some minor alignment or look and feel problem.
Priority is when the bugs will be rectified.
Severity is decided by the testers and priority is decided by the developers.

30.    Can Automation testing replace manual testing? If it so, how?
No automation cannot replace manual testing. Only if an application is stable can we go for automation. To find whether an application is stable we need to do Manual testing.

31.    What is a test case?
Test case is derived from a test condition and it tells what functionality we are going to test for a given condition and the expected result.

32.    What is a test condition?
Test condition is derived from BR/FS, which reflects the actual customer requirements.

33.    What is the test script?
It tells us the flow or a step-by-step process that we are going to execute along with the test data.

34.    What is the test data?
It is a data that we are going to use to test a particular functionality.

35.    What is an Inconsistent bug?
If we get a bug that cannot be simulated or it come some times only then it is called inconsistent bug.
36.    What is the difference between Re-testing and Regression testing?
Retesting is one which is done fully and regression is one it is done related to a bug and the places it can have an impact.

37.    What are the different types of testing techniques?
Equivalence Class Partisan, Boundary Value Analysis, Error Guessing.

38.    What are the risks involved in testing?
Schedule Risk
Resource Risk
Technology Risk

39.    Differentiate Test bed and Test Environment?
Test bed is initial data that is entered to start testing. Test Environment is the environment in which we are going to test the application.

40.    What is the difference between quality and testing?
Quality is a process to deliver a bug free product. Testing is a part of quality.

41.    What is the difference between White & Black Box Testing?
White box is used for code checking and see the flow of loops.
Black box we do a functionality testing without looking at the coding.

42.    What is the difference between Quality Assurance and Quality Control?
Quality control is a process by which actually helps us in delivering a product that is bug free and maintains some standards.
Quality Control is a process by which we maintain certain standard so that we develop a product which will have some pre defined standards.

43.    What is the difference between Testing and debugging?
Testing is a process by which we identify the bugs and debugging is a process by which the developers identify the bugs and rectifies it.

44.    What is the difference between bug and defect?
Defect is a deviation from the FS/BR. A bug is an error found in the application.

45.    What is the difference between verification and validation?
Verification asks, "Is the product being built right?" It is the process of determining whether or not the products of a given phase of the software development cycle fulfill the established requirements. Validation asks, "Is the right product being built?" It evaluates software at the end of the development lifecycle to ensure that the product not only complies with standard safety requirements and the specific criteria set forth by the customer, but performs exactly as expected.

46.    What is the difference between functional spec. and Business requirement specification?
Functional specification is used for SIT and Business requirement is used for UAT.  FS is more technical used for development process and BR is more useful towards the analysis point.



47.    What is the difference between unit testing and integration testing?
Unit is the basic level of testing and tries to validate more towards field level validation. Integration testing is done at a module level.

48.    What is the diff between Volume & Load?
In volume number of transaction is increased and the no of user constant in load the no user will be increased and transaction is kept constant.

49.    What is diff between Volume & Stress?
In volume number of transaction is increased and the no of user is constant in stress both user and transaction is increased.

50.    What is the diff between Stress & Load Testing?
In stress both user and transaction is increased in load the no user will be increased and transaction is kept constant.

51.    What is the Diff between Two Tier & Three tier Architecture?
Business/ application logic resides in a separate system in 3 tier where as in 2 tier it resides in the front end system.

52.    What is the diff between Client Server & Web Based Testing?
Client server it is a controlled environment we concentrate more at the functionality where as in web based we check more towards the security of the application.

53.    What is the diff between Integration & System Testing?
Integration testing we test the interfaces in system testing we test the functionality.

54.    What is the Diff between static and dynamic?
Static Testing: Analysis of a program carried out without executing the program.
Dynamic Testing: Testing software through executing it.

55.    What is the diff between alpha testing and beta testing?
Alpha testing is done by user is performed at the development site.
Beta testing is done by user is performed at the client site.

56.    What are the Minimum requirements to start testing?
The application should be stable to start testing.

57.    What is Smoke Testing & when it will be done?
Smoke testing is like adhoc testing and it is normally done at the sanity testing level or during the last stage of testing to see that no error is there in the application.

58.    What is Adhoc Testing? When it can be done?
Adhoc testing is a free form testing it can be done if we do not have much information about the application or during the normal testing process also for it helps to find some defects that are not covered in the conditions.




59.    What is security testing?
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

60.    What is database testing?
To check if the data base get updated once a transaction is posted in the front end and also to see if the data gets updated in the data base correctly.

61.    What is the relation ship between Quality & Testing?
Testing is a part of quality and testing tell us how to improve the quality of a product and where we have to concentrate.

62.    How do you determine, what to be tested?
Based on the FS and the priority of the modules that need to delivered we determine what needs to be tested.

63.    How do you go about testing a project?
Start with the initiation, planning, execution, defect management and test closure.

64.    What is the Initial Stage of testing?
Initiation.

65.    What is Web Based Application Testing?
Web Based Application Testing is End-to-end system testing with dynamically created test actions based on results from previous test actions.

66.    What is Two Tier & Three tier Architecture?
2 Tier: Refers to client/server architectures in which the user interface runs on the client and the database is stored on the server. The actual application logic can run on either the client or the server.
3 Tier: A special type of client/server architecture consisting of three well-defined and separate processes, each running on a different platform:

a.    The user interface, which runs on the user's computer (the client).
b.    The functional modules that actually process data. This middle tier runs on a server and is often called the application server.
c.    A database management system (DBMS) that stores the data required by the middle tier. This tier runs on a second server called the database server.

67.    What is the use of Functional Specification?
It gives an over view of the application and helps us in planning, estimation, duration and helps us in writing test case and conditions.

68.    Why do we prepare test condition, test cases, and test script (Before Starting Testing)?
To deliver a good product and also to show that we have covered all the scenarios in the application and we have fully covered the application.

69.    Is it not waste of time in preparing the test condition, test case & Test Script?
No

70.    How do you go about testing of Web Application?
To concentrate more towards the security and loading of different pages and links.

71.    How do you go about testing of Client Server Application?
To concentrate more towards the functionality part.

72.    What is meant by Static Testing?
It is testing without executing, just a walk through of the application.

73.    Can the static testing be done for both Web & Client Server Application?
Yes

74.    In the Static Testing, what all can be tested?
Baseline documents, test deliverables before test execution and closer.

75.    Can test condition, test case & test script help you in performing the static testing?
Yes
76.    What is meant by dynamic testing?
Is normal testing done by executing the application.

77.    Is the dynamic testing a functional testing?
Yes

78.    Is the Static testing a functional testing?
No

79.    What are the functional testing you perform?
SIT

80.    What is meant by Alpha Testing?
Alpha testing is done by user is performed at the development site.

81.    What kind of Document you need for going for an Functional testing?
Functional Specification.

82.    What is meant by Beta Testing?
Beta testing is done by user is performed at the client site.

83.    At what stage the unit testing has to be done?
It is done at the initial stage after completing the coding and we find the application to be stable.

84.    Who can perform the Unit Testing?
Normally the developers are better to do unit testing. If it is not done by them then it can be done by the testers.

85.    When will the Verification & Validation be done?
Verification before testing and validation during testing.




86.    What is meant by Code Walkthrough?
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

87.    What is meant Code Review?
A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards. It is also called as Code Inspection.

88.    What is the testing that a tester performs at the end of Unit Testing?
Integration Testing.

89.    What are the things, you prefer & Prepare before starting Testing?
Understanding the application fully, test conditions, test case, test data, traceability matrix.

90.    What is Integration Testing?
IT checks to see the integration (flow of information from one module to another) between different modules.

91.    What is Incremental Integration Testing?
Module by module testing is Incremental Integration Testing.

92.    What is meant by System Testing?
System testing is functional testing.

93.    What is meant by SIT?
System Integration Testing.

94.    When do you go for Integration Testing?
Once unit testing is done and application is stable.

95.    Can the System testing be done at any stage?
No only after we complete unit it is advisable to go for System testing.

96.    What are stubs & drivers?
Stub: A skeletal or special-purpose implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it.
Driver: A program or test tool used to execute software against a test case suite.

97.    What is the final Stage of Integration Testing?
SIT.

98.    Where in the SDLC, the Testing Starts?
After Coding.

99.    What is the Outcome of Integration Testing?
A stable application that can be sent to production for SIT.

100.    What is meant by GUI Testing?
To check for GUI components and the their functionality.

101.    What is meant by Back-End Testing?
It is database testing.

102.    What is Compatibility Testing?
Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

103.    What is Usability Testing?
Usability testing is to see how good the product is as per the requirements of the customer and also to see how user friendly the product is.

104.    What is the Importance of testing?
To deliver a bug free product as per the requirement of the client.

105.    What is meant by regression Testing?
Regression Testing is used to check the status of bugs that we sent top developers and to see if they have any impact due to the rectification of the bugs sent.

106.    When we prefer Regression & what are the stages where we go for                                                                                Regression Testing?
After the fixing of the defects by the developers we go for regression.

107.    What is performance testing?
It is testing to see what happens to the application under different loads of data.

108.    What is the Performance testing; those can be done Manually & Automatically?
It is testing to see what happens to the application under different loads of data. It is normally done using tools (automation).

109.    What is Volume, Stress & Load Testing?
In volume number of transaction is increased and the no of user constant in load the no user will be increased and transaction is kept constant in stress both user and transaction is increased.

110.    What is a Bug?
It is a defect in the product that dose not match with the FS or the expected result.

111.    What is a Defect?
It is a deviation from the FS that lead to error.

112.    What is the defect Life Cycle?
It tells us what happens after a bug is raised by the tester.

113.    What is the Priority in fixing the Bugs?
Critical bugs are normally fixed first followed by medium and then low normally.


114.    Explain the Severity you rate for the bugs found?
Severity is to tell how whether the bug is Critical, Medium, or Low If it is critical it is a show stopper if it is medium it has some functional problem but can proceed if it is low some minor alignment or look and feel problem.

115.    Diff between UAT & IST?
For UAT we use the BR, for IST we use the FS.

UAT is done normally by the end user with a good domain knowledge and IST by the Testers.

In IST we do testing based on condition and in UAT it will be mostly done in scenario based.

116.    What is meant by UAT?
It is User Acceptance Testing.

117.    What all are the requirements needed for UAT?
Sit should have been done, BR document should be available.

118.    What is risk analysis?
It helps us to find what are the risks associated with a project.
Schedule Risk
Resource Risk
Technology Risk

119.    How to do risk management?
By finding out the expected risk before testing.

120.    What are test closure documents?
Test Closure Documents like Test Case, Test Conditions, Traceability Matrix, Defect Report, Test Summary Report, Test Data and Down Time Report.

121.    What is traceability matrix?
It is document which tells whether we have tested completely.

122.    What ways you followed for defect management?
We used tracebility matrix and Orbi Solve.