Smoke Test:
When a build is received, a smoke test is run to ascertain if the build is stable and it can be considered for further testing. Smoke testing can be done for testing the stability of any interim build. Smoke testing can be executed for platform qualification tests.
Sanity testing:
Once a new build is obtained with minor revisions, instead of doing a through regression, a sanity is performed so as to ascertain the build has indeed rectified the issues and no further issue has been introduced by the fixes. Its generally a subset of regression testing and a group of test cases are executed that are related with the changes made to the app. Generally, when multiple cycles of testing are executed, sanity testing may be done during the later cycles after through regression cycles.
1. Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
2. A smoke test is scripted--either using a written set of tests or an automated test
A sanity test is usually unscripted.
3. A Smoke test is designed to touch every part of the application in a cursory way. It's is shallow and wide.
A Sanity test is used to determine a small section of the application is still working after a minor change.
4. Smoke testing will be conducted to ensure whether the most crucial functions of a program work, but not bothering with finer details. (Such as build verification).
Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
5. Smoke testing is normal health check up to a build of an application before taking it to testing in depth.
Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.
Wednesday, August 5, 2009
Friday, July 31, 2009
Quality Assurance Vs Quality Control
Quality Assurance Vs Quality Control
Quality Control:
The operational techniques and activities that are used to fulfill requirements for quality. QC has following features:
• QC is Product Oriented.
• QC is a Reactive Approach.
• QC is a Line Function.
• QC is towards Defect Detection.
• E.g. Walkthrough, Testing, Inspection, Code Review etc.
Typical Quality Control contains following steps:
• Problem Identification
• Problem Analysis
• Problem Correction
• Feedback to QA
Quality Assurance:
All those planned and systematic activities implemented to provide adequate confidence that an entity will fulfill requirements for quality. QA has following features:
• QA is Process Oriented.
• QA is a Proactive Approach.
• QA is a Staff Function.
• QA is towards Defect Prevention.
• E.g. Quality Audits, Defining Process, Tool Selection, Trainings etc.
Typical Quality Assurance Contains following steps:
• Data Gathering (Input from QC)
• Problem trend analysis
• Process Identification
• Process Analysis
• Process Improvement
Quality Control:
The operational techniques and activities that are used to fulfill requirements for quality. QC has following features:
• QC is Product Oriented.
• QC is a Reactive Approach.
• QC is a Line Function.
• QC is towards Defect Detection.
• E.g. Walkthrough, Testing, Inspection, Code Review etc.
Typical Quality Control contains following steps:
• Problem Identification
• Problem Analysis
• Problem Correction
• Feedback to QA
Quality Assurance:
All those planned and systematic activities implemented to provide adequate confidence that an entity will fulfill requirements for quality. QA has following features:
• QA is Process Oriented.
• QA is a Proactive Approach.
• QA is a Staff Function.
• QA is towards Defect Prevention.
• E.g. Quality Audits, Defining Process, Tool Selection, Trainings etc.
Typical Quality Assurance Contains following steps:
• Data Gathering (Input from QC)
• Problem trend analysis
• Process Identification
• Process Analysis
• Process Improvement
Thursday, July 30, 2009
RFT Interview Questions
Q1: What are the main features of Functional Tester:
Ans:
-Complete functional testing of the application
- test the state of objects through verification points.
- Testing any object in the application, including the object's properties and its data.
- Creating and editing simple object-oriented test scripts.
- Generating code through wizards, for example automatically creating a verification point through wizard.
Q. 2: What Process is followed by Rational Functional Tester for test automation?
Ans. Recording of Test Scripts, Enhancing the Test Scripts and then Playing Back the Scripts
Q. 3: For how many development platforms & Languages Functional Tester is available?
Ans.
- Java Scripting uses the Java language and the IBM Rational Software Development Platform.
- VB.NET Scripting uses the VB.NET language and the Microsoft Visual Studio .NET development environment.
Q. 4: What is benefit of test object map in Rational Functional Tester?
Ans. Test object map gets created automatically when recording the script for the application under test. It provides quick way to add objects to a script. It creates a list of test objects available in the application whether they are currently displayed or not. We can create a new test object map either by basing it on an existing map or by adding objects as required. It contains recognition properties for every object; so we can update the recognition information in one central location. Therefore, any scripts using this test object map shall be able to share the updated information. Test object maps created for HTML applications are more hierarchical than those created for Java applications. A browser is the top level of the test object map and the HTML application is inside the browser.
Q. 5: How various objects are identified by Functional Tester?
Ans. In Functional Tester object-oriented technology is used to identify various objects by their internal object properties and not by their screen coordinates. Thus even if the location or text of an object changes, the Functional Tester can still find it on playback.
Q. 6: In how many ways we can test the applications on Linux using RFT?
Ans.
First Way: We can record a script on Windows Environment and export it to Linux & then play it back on Linux.
Second Way: By writing scripts using the Test Object Insert tool. Instead of creating an object map through recording we populate it outside of the recorder by opening the map and selecting objects in the test application.
We can insert verification points without recording, by opening the Verification Point wizard from the Script Explorer.
Q. 7: What are two types of TestManagers in RFT?
Ans.
1) TestManager: It includes the Test Manager Log, running Windows & Linux remote playback agents and test management features like running scripts as part of a test suite. Functional Tester has its own logs and does not depend on the TestManager log integration.
2) ClearQuest Test Manager: It helps us in associating functional test scripts to Test Cases and executes them. Using CQTM we can analyze the received execution results and record those results for reporting and analysis.
Q. 8: What is a Rational and Functional Test project?
Ans.
- Rational Test project is used for storing test assets like test plans test cases, test logs, reports, builds etc. To associate a Functional Tester project with a Rational project, a Rational project needs to be created to store the test assets. Functional Test project stores all application test assets like scripts, object maps, verification point baseline files and script templates. Functional Test project is created before recording the scripts.
Q. 9: What is the use of associating a project with TestManager in RFT?
Ans.
- 1) Creating and playingback the scripts from within Rational TestManager.
2) Using the TestManager Agent for playing back scripts on remote computer.
3) You can view the scripts from the Test Scripts window of Rational TestManager.
Q. 10: Benefits of associating a Functional Tester project with Rational Project.
Ans.
1) Management of testing assets from one Rational project.
2) You can record and play back all Functional Tester scripts from Rational TestManager.
3) Playing back Functional Tester script on different computer using Rational Test Agents through TestManager.
4) Management Functional Tester logs using the Test Log window of TestManager.
5) Use of Test Manager reports to get information about the results of running Functional Tester test script and get coverage report for testing project.
6) Use TestManager suite to coordinate the way that scripts run.
Q. 11: Are there any restrictions when we disassociate a project from the current Rational project?
Ans. Yes. We can not play back Functional Tester script or test cases or suites that include Functional Tester scripts in disassociated project from TestManager. Test Manager deletes test script source from the disassociated project. This operation can not be undo. If we associate Functional Test project with Rational project again, TestManager creates new test script source.
Q. 12: Name three buttons available in Functional Tester Projects view banner.
Ans.
- Connect to Functional Test Project: It allows us to connect to an existing Functional Tester project.
- Refresh Projects: It enables us to repaint the display to reflect changes.
- Synchronize with Editor: It scrolls in the tree hierarchy to the name of the script currently displayed in the Java Editor.
Q. 13: Can we export Functional Test project items?
Ans. We can export project items like scripts, test object maps, Java files, Visual Basic files and data pools to another Functional Tester project. When we export a script Functional Tester includes all necessary files like shared test object maps even though it was not selected by us.
Q. 14: What is the utility of a verification points in Rational Functional Tester?
Ans. During the recording verification points can be inserted in the script to confirm the state of an object in the application.
A verification point captures the object information based upon the type of verification point and stores it in a baseline data file. The information in the base file becomes baseline of expected state of object during subsequent builds.
Q. 15: What types of verification points are provided by RFT?
Ans.: Rational Functional Tester has two types of verification points: Object properties verification point and Data verification points. Data verification point has five further points: Menu hierarchy verification point, Table verification point, Text verification point, Tree hierarchy verification point, List verification point.
Q. 16: How RFT playback depends upon the platform and the browser?
Ans.: Test playback in RFT is independent of the platform as well as independent of browser. E.g. we can record script on Windows and play it back on Linux. Also, the script contains no references to the browser during the recording, we can play back the script using any of the supported versions of Firefox, Mozilla, Internet Explorer or Netscape.
Q. 17: What host & test platforms supported by RFT?
Ans. Functional Tester runs on the following Host and Test platforms: Windows XP Professional, Windows 2000 Professional & Server, Windows 2000 Server & Advanced Server, Windows 2003 Enterprise, Standard & Server
Platforms supporting all functions of RFT except the recording: Red Hat Linux Enterprise Workstation 4.0, SuSE Linux Professional version 9.0, SuSE Linux Enterprise Server 10.0, Novel Desktop 10.0
Q. 18: What types of nesting of objects is supported by Functional Tester?
Ans. Parent-child nesting and Owner-owned nesting
Q. 19: Type of file extensions created while exporting Functional Test project items?
Ans. RFT compresses a copy of the files into a data transfer file with the name specified by us. It also appends a .rftjdtr (Functional Tester Java Scripting) or .rftvdtr (Functional Tester VB.NET Scripting) extension to it.
Q. 20: What is the helper superclass in RFT?
Ans. All Functional Tester scripts use default helper superclass. These scripts extend the RationalTestScript class and thereby inherit a number of methods. However, advanced users can create their own helper superclass (if they want to add additional methods or override the methods within RationalTestScript).
Q. 21: Name the Functional Test project items that can be imported?
Ans. Project items like scripts, test object maps, Java files or Visual Basic files, and datapools can be imported into a Functional Tester project. Functional Tester adds all the project items from the data transfer file into the project specified by us. We can use any file compression program which support the .zip to view and work with items in the data transfer file.
Q. 22: RFT provides how many type of delete Cookies methods?
Ans.
- Method of deleting all cookies for the current profile or user
- Method of deletes cookies in a specific page or domain for the current profile or user
Q. 23: How an application starts during recording the tests?
Ans. While recording tests the application can be started by using startApp command. It makes playing back the tests more reliable because startApp uses the application configuration information. RFT will open either Java applications that we specify or HTML pages in our browser, or run applications in executable form.
Q. 24: What is a test project in RFT?
Ans. Location where Functional Tester keeps all of the scripts, along with expected and actual results is called as a test project. The format of test project is governed by the environment being used.
Note: If you are using the Java language, create a Java test project. However you are using Visual Basic.NET, create a .NET test project.
Q. 25: How can we create a new RFT script without recording?
Ans. In new script > RFT includes import statements for files we need to compile the script and comments containing information of archiving. Functional Tester uses the script name as the class name and sets up testMain. Here, you can add the commands to include in the script.
Q. 26: Can we do recording in an existing RFT script?
Ans. Yes. We can do the recording in existing RFT script by bringing our cursor to the desired location & just start the recording. Start the application >> insert verification points >> and add all script support functions.
Q. 27: How can we record script for testing the HTML applications using RFT?
Ans.
- Enabling the Web browser: Enabling of the browser can be done by clicking on Configure > "Enable Environments for Testing". This will enable the environments for testing.
- Configuring the HTML applications for testing: It can be done by clicking on Configure > "Configure Applications for Testing" to specify information about our application and its environment. For testing MS HTML Applications (MSHTA), we need to run mshta.exe to configure application desired to be tested.
Ans:
-Complete functional testing of the application
- test the state of objects through verification points.
- Testing any object in the application, including the object's properties and its data.
- Creating and editing simple object-oriented test scripts.
- Generating code through wizards, for example automatically creating a verification point through wizard.
Q. 2: What Process is followed by Rational Functional Tester for test automation?
Ans. Recording of Test Scripts, Enhancing the Test Scripts and then Playing Back the Scripts
Q. 3: For how many development platforms & Languages Functional Tester is available?
Ans.
- Java Scripting uses the Java language and the IBM Rational Software Development Platform.
- VB.NET Scripting uses the VB.NET language and the Microsoft Visual Studio .NET development environment.
Q. 4: What is benefit of test object map in Rational Functional Tester?
Ans. Test object map gets created automatically when recording the script for the application under test. It provides quick way to add objects to a script. It creates a list of test objects available in the application whether they are currently displayed or not. We can create a new test object map either by basing it on an existing map or by adding objects as required. It contains recognition properties for every object; so we can update the recognition information in one central location. Therefore, any scripts using this test object map shall be able to share the updated information. Test object maps created for HTML applications are more hierarchical than those created for Java applications. A browser is the top level of the test object map and the HTML application is inside the browser.
Q. 5: How various objects are identified by Functional Tester?
Ans. In Functional Tester object-oriented technology is used to identify various objects by their internal object properties and not by their screen coordinates. Thus even if the location or text of an object changes, the Functional Tester can still find it on playback.
Q. 6: In how many ways we can test the applications on Linux using RFT?
Ans.
First Way: We can record a script on Windows Environment and export it to Linux & then play it back on Linux.
Second Way: By writing scripts using the Test Object Insert tool. Instead of creating an object map through recording we populate it outside of the recorder by opening the map and selecting objects in the test application.
We can insert verification points without recording, by opening the Verification Point wizard from the Script Explorer.
Q. 7: What are two types of TestManagers in RFT?
Ans.
1) TestManager: It includes the Test Manager Log, running Windows & Linux remote playback agents and test management features like running scripts as part of a test suite. Functional Tester has its own logs and does not depend on the TestManager log integration.
2) ClearQuest Test Manager: It helps us in associating functional test scripts to Test Cases and executes them. Using CQTM we can analyze the received execution results and record those results for reporting and analysis.
Q. 8: What is a Rational and Functional Test project?
Ans.
- Rational Test project is used for storing test assets like test plans test cases, test logs, reports, builds etc. To associate a Functional Tester project with a Rational project, a Rational project needs to be created to store the test assets. Functional Test project stores all application test assets like scripts, object maps, verification point baseline files and script templates. Functional Test project is created before recording the scripts.
Q. 9: What is the use of associating a project with TestManager in RFT?
Ans.
- 1) Creating and playingback the scripts from within Rational TestManager.
2) Using the TestManager Agent for playing back scripts on remote computer.
3) You can view the scripts from the Test Scripts window of Rational TestManager.
Q. 10: Benefits of associating a Functional Tester project with Rational Project.
Ans.
1) Management of testing assets from one Rational project.
2) You can record and play back all Functional Tester scripts from Rational TestManager.
3) Playing back Functional Tester script on different computer using Rational Test Agents through TestManager.
4) Management Functional Tester logs using the Test Log window of TestManager.
5) Use of Test Manager reports to get information about the results of running Functional Tester test script and get coverage report for testing project.
6) Use TestManager suite to coordinate the way that scripts run.
Q. 11: Are there any restrictions when we disassociate a project from the current Rational project?
Ans. Yes. We can not play back Functional Tester script or test cases or suites that include Functional Tester scripts in disassociated project from TestManager. Test Manager deletes test script source from the disassociated project. This operation can not be undo. If we associate Functional Test project with Rational project again, TestManager creates new test script source.
Q. 12: Name three buttons available in Functional Tester Projects view banner.
Ans.
- Connect to Functional Test Project: It allows us to connect to an existing Functional Tester project.
- Refresh Projects: It enables us to repaint the display to reflect changes.
- Synchronize with Editor: It scrolls in the tree hierarchy to the name of the script currently displayed in the Java Editor.
Q. 13: Can we export Functional Test project items?
Ans. We can export project items like scripts, test object maps, Java files, Visual Basic files and data pools to another Functional Tester project. When we export a script Functional Tester includes all necessary files like shared test object maps even though it was not selected by us.
Q. 14: What is the utility of a verification points in Rational Functional Tester?
Ans. During the recording verification points can be inserted in the script to confirm the state of an object in the application.
A verification point captures the object information based upon the type of verification point and stores it in a baseline data file. The information in the base file becomes baseline of expected state of object during subsequent builds.
Q. 15: What types of verification points are provided by RFT?
Ans.: Rational Functional Tester has two types of verification points: Object properties verification point and Data verification points. Data verification point has five further points: Menu hierarchy verification point, Table verification point, Text verification point, Tree hierarchy verification point, List verification point.
Q. 16: How RFT playback depends upon the platform and the browser?
Ans.: Test playback in RFT is independent of the platform as well as independent of browser. E.g. we can record script on Windows and play it back on Linux. Also, the script contains no references to the browser during the recording, we can play back the script using any of the supported versions of Firefox, Mozilla, Internet Explorer or Netscape.
Q. 17: What host & test platforms supported by RFT?
Ans. Functional Tester runs on the following Host and Test platforms: Windows XP Professional, Windows 2000 Professional & Server, Windows 2000 Server & Advanced Server, Windows 2003 Enterprise, Standard & Server
Platforms supporting all functions of RFT except the recording: Red Hat Linux Enterprise Workstation 4.0, SuSE Linux Professional version 9.0, SuSE Linux Enterprise Server 10.0, Novel Desktop 10.0
Q. 18: What types of nesting of objects is supported by Functional Tester?
Ans. Parent-child nesting and Owner-owned nesting
Q. 19: Type of file extensions created while exporting Functional Test project items?
Ans. RFT compresses a copy of the files into a data transfer file with the name specified by us. It also appends a .rftjdtr (Functional Tester Java Scripting) or .rftvdtr (Functional Tester VB.NET Scripting) extension to it.
Q. 20: What is the helper superclass in RFT?
Ans. All Functional Tester scripts use default helper superclass. These scripts extend the RationalTestScript class and thereby inherit a number of methods. However, advanced users can create their own helper superclass (if they want to add additional methods or override the methods within RationalTestScript).
Q. 21: Name the Functional Test project items that can be imported?
Ans. Project items like scripts, test object maps, Java files or Visual Basic files, and datapools can be imported into a Functional Tester project. Functional Tester adds all the project items from the data transfer file into the project specified by us. We can use any file compression program which support the .zip to view and work with items in the data transfer file.
Q. 22: RFT provides how many type of delete Cookies methods?
Ans.
- Method of deleting all cookies for the current profile or user
- Method of deletes cookies in a specific page or domain for the current profile or user
Q. 23: How an application starts during recording the tests?
Ans. While recording tests the application can be started by using startApp command. It makes playing back the tests more reliable because startApp uses the application configuration information. RFT will open either Java applications that we specify or HTML pages in our browser, or run applications in executable form.
Q. 24: What is a test project in RFT?
Ans. Location where Functional Tester keeps all of the scripts, along with expected and actual results is called as a test project. The format of test project is governed by the environment being used.
Note: If you are using the Java language, create a Java test project. However you are using Visual Basic.NET, create a .NET test project.
Q. 25: How can we create a new RFT script without recording?
Ans. In new script > RFT includes import statements for files we need to compile the script and comments containing information of archiving. Functional Tester uses the script name as the class name and sets up testMain. Here, you can add the commands to include in the script.
Q. 26: Can we do recording in an existing RFT script?
Ans. Yes. We can do the recording in existing RFT script by bringing our cursor to the desired location & just start the recording. Start the application >> insert verification points >> and add all script support functions.
Q. 27: How can we record script for testing the HTML applications using RFT?
Ans.
- Enabling the Web browser: Enabling of the browser can be done by clicking on Configure > "Enable Environments for Testing". This will enable the environments for testing.
- Configuring the HTML applications for testing: It can be done by clicking on Configure > "Configure Applications for Testing" to specify information about our application and its environment. For testing MS HTML Applications (MSHTA), we need to run mshta.exe to configure application desired to be tested.
SOFTWARE TESTING PROCESS
SOFTWARE TESTING PROCESSES
Software Testing is now become the most important activity that need to be completed before any new product go live into the open market. Due to increased IT Companies & New Technologies every day in different part of globes it is not easy to lead the market without improving your existing Product Quality and off course the new launches.
Every organization has its own QA (Quality Assurance) model/process that is followed up but still there are some basic steps that need to be taken care of while defining the processes for developing good Quality Products which is the important requirement that need to be fulfilled before any product go live into the market.
Find below the list of activities that need to be performed during Testing Cycle of any Product/Project:
Get PRD (Project Requirement Document) from the Client.
Review the PRD document and provide Review Comments on PRD Doc.
Make sure that all the issues get resolved before PRD Doc is marked as Baseline.
Prepare Test Plan using PRD Doc and send it to client.
Update the Test Plan Doc as per the client feedback.
Now start with the Use Case Doc created by BA (Business Analyst) & SA (System Analyst).
Review the Use Case doc and provide review comments.
Once Use Case doc is baseline start creating the Test Case against Use Cases.
Perform Smoke Testing of QA Build before accepting it into the QA for further Testing.
Once Smoke Test is passed for QA Build start executing the Test Cases for implemented features.
Log defects in Defect Tracking tool (i.e. Rational Clear Quest, Bugzilla, JIRA) for all he failed scenario.
Submit Test Summary Report at the completion of every Testing Cycle.
Start with Retesting of defects when you receive the next QA Build for testing.
Start Test Case execution for new features.
Once Test Case execution for new features are done start with regression testing to check if there is any code break due to implementation of new features.
Software Testing is now become the most important activity that need to be completed before any new product go live into the open market. Due to increased IT Companies & New Technologies every day in different part of globes it is not easy to lead the market without improving your existing Product Quality and off course the new launches.
Every organization has its own QA (Quality Assurance) model/process that is followed up but still there are some basic steps that need to be taken care of while defining the processes for developing good Quality Products which is the important requirement that need to be fulfilled before any product go live into the market.
Find below the list of activities that need to be performed during Testing Cycle of any Product/Project:
Get PRD (Project Requirement Document) from the Client.
Review the PRD document and provide Review Comments on PRD Doc.
Make sure that all the issues get resolved before PRD Doc is marked as Baseline.
Prepare Test Plan using PRD Doc and send it to client.
Update the Test Plan Doc as per the client feedback.
Now start with the Use Case Doc created by BA (Business Analyst) & SA (System Analyst).
Review the Use Case doc and provide review comments.
Once Use Case doc is baseline start creating the Test Case against Use Cases.
Perform Smoke Testing of QA Build before accepting it into the QA for further Testing.
Once Smoke Test is passed for QA Build start executing the Test Cases for implemented features.
Log defects in Defect Tracking tool (i.e. Rational Clear Quest, Bugzilla, JIRA) for all he failed scenario.
Submit Test Summary Report at the completion of every Testing Cycle.
Start with Retesting of defects when you receive the next QA Build for testing.
Start Test Case execution for new features.
Once Test Case execution for new features are done start with regression testing to check if there is any code break due to implementation of new features.
Subscribe to:
Posts (Atom)