PagKis - Software Testing

RSS Feed Homepage

Articles: 1, 2

Test Specification
2007-12-05 04:17:00
Test Specification – It is a detailed summary of what scenarios will be tested, how they will be tested, how often they will be tested, and so on and so forth, for a given feature. Trying to include all Editor Features or all Window Management Features into one Test Specification would make it too large to effectively read.However, a Test Plan is a collection of all test specifications for a given area. The Test Plan contains a high-level overview of what is tested for the given feature area. Contents of a Test Specification:Revision History - This section contain information like Who created the test specification? When was it created? When was the last time it was updated? Feature Description – A brief description of what area is being tested.What is tested? – An overview of what scenarios are tested.What is not tested? - Are there any areas that are not being tested. There can be several reasons like... being covered by different people or any test limitations etc. If so, ...
More About: Test

When requirements are changing continuously
2007-11-30 04:59:00
My this post is about what should be our approach when requirements are changing continuously. Work with end users and management early on to understand how requirements might change, so that alternate test plans and strategies can be worked out in advance. It is helpful if the application's initial design allows for some adaptability, so that later changes do not require re-doing the whole work from scratch. Below are some more points that might help:Devote appropriate effort to risk analysis of changes, in order to minimize regression-testing needs.In the project's initial stages, allow for some extra time to commensurate with probable changes.Balance the effort put into setting up automated testing with the expected effort required to redo them to deal with changes.Design some flexibility into test cases; this is not easily done; the best bet is to minimize the detail in the test cases, or set up only higher-level generic-type test plans.Focus less on detailed test plans and te...
More About: Changing

Software Testing Estimation Process
2007-11-23 11:09:00
Software Testing estimation process is one of the most difficult and critical activity. When say that one project will be completed in a particluar time at a particular cost, then it must happen. If it does not happen, it may result in peer's comments and senior management’s warnings to being fired depending on the reasons and seriousness of the failure. Here are a few rules for effective software testing estimation:- Estimation must be based on previous projects. All estimation should be based on previous projects. - Estimation must be recorded. All decisions should be recorded. It is very important because if requirements change for any reason, the records would help the testing team to estimate again. - Estimation shall be always based on the software requirements. All estimation should be based on what would be tested. The software requirements shall be read and understood by the testing team as well as development team. Without the testing participation, no serious estimati...
More About: Software , Process , Imation

Defect Removable Efficiency
2007-11-16 05:59:00
The Defect Removable Efficiency (DRE) is the percentage of defects that have been removed during an activity, computed with the equation below:DRE = (Number of Defects Removed / Number of Defects at Start of Process) * 100The DRE can also be computed for each software development activity and plotted on a bar graph to show the relative defect removal efficiencies for each activity. Or, the DRE may be computed for a specific task or technique (e.g. design inspection, code walkthrough, unit test, 6 month operation, etc.)We can also calculate DRE as:DRE = A / (A+B)where A = Defects by raised by testing team and B = Defects raised by customer If dre

Testing at Programming / Coding phase
2007-11-05 10:46:00
Note: This is applicable for both Black box as well as White box testers.Check the code for consistency with design - The areas to check include modular structure, module interfaces, data structures, functions, algorithms and I/O handling.Start testing with organized and systematic manner - Perform the Testing process in an organized and systematic manner with test runs dated, annotated and saved. A plan or schedule can be used as a checklist to help the programmer organize testing efforts. If errors are found and changes made to the program, all tests involving the erroneous segment (including those which resulted in success previously) must be rerun and recorded.Asks some colleague for assistance - Some independent party, other than the programmer of the specific part of the code, should analyze the development product at each phase. The programmer should explain the product to the party who will then question the logic and search for errors with a checklist to guide the search. T...
More About: Programming , Coding , Phase , Hase

Regression Testing
2007-11-01 03:42:00
Definition - Regression testing is the re-running of Test cases that a program has previously executed correctly, in order to detect failures spawned by changes or corrections made during software development and maintenance.These failures arise from incomplete or incorrect changes and are often witnessed as (unexpected) side effects in apparently unrelated application areas. It is common in the IT industry, that one in six (or seventeen percent*) of correction attempts are themselves defective. This high rate of introduced defects is exaggerated when developers maintain a large number of poorly documented, integrated systems where they of ten have little or no experience of these systems. Regression testing may then be used to great effect at detecting subtle side effects and unconsidered inter-relationships within these environments, thus reducing risk. In regression testing standard actions in a test procedure are carried out and the expected responses are checked for correctness...
More About: Testing

CSTE Sept 16th 2006
2007-10-29 11:48:00
Part 1 - Objective – 50 Questions – 45 Min.Part 2 - Subjective – 10 Questions – 75 Min.Part 3 - Objective – 50 Questions – 45 Min.Part 4 - Subjective – 10 Questions – 75 Min.Objective Questions1. As a general rule, __________ measures are much more important.a. Subjectiveb. Objective 2. If the measurement taken by the two people are same refers to the term asa. Reliabilityb. Validityc. Calibrationd. Ease of Use and Simplicity3. The term __________ refers the degree to which a measure actually measures what it was intended to measure.a. Reliabilityb. Validityc. Calibrationd. Ease of Use and Simplicity4. When basic quality aspects have been identified the “standards” should be defined bya. IT Teamb. Project Managerc. Quality Assurance personald. Managemente. Development Team5. The “standards” for the software developed using new technology should be defined bya. IT Teamb. Project Managerc. Quality Assurance personald....
More About: Sept

Openings in US / Singapore
2007-10-27 07:43:00
Date: November 01, 2007There is an opening in Singapore for software testing professionals having experince of 3-5 years in software testing.Below are job details:Degree in IT, Engineering or other related discipline At least 3-5 years of quality assurance and software testing experience Prior experience in Oracle/SQL and testing field devices /instruments. Good understanding of software development process Good command of English A team player and enjoy interacting with people of all levels in a multicultural environmentLocation: South/CentralIf you are interested, please mail your resume at pagkis_testing_jobs@yahoo.com with the subject line as "Singapore: Testing-SC"

Openings with us !!
2007-10-27 07:41:00
Coming Soon... !!

For Freshers
2007-10-27 07:40:00
We have some requirements at freshers level (for Software Testing only).2006 and 2007 passout candidates can send their CV at pagkis_testing_jobs@yahoo.comIn subject line, write: Fresher

Urgents Requirements !!
2007-10-27 07:19:00
========================================= ==================We have Urge nt requirements for Software Test Professionals. Below are job details:Client: WILL BE DISCLOSED OVER PHONEExperince: 3+Location: Gurgaon, Delhi and NoidaSkills Required:Experince on Manual TestingKnowledge of Automation Tools such as Mercury WinRunner, QTP, Load Runner, Test Director etc.Defect/Bug Tracking and reporting Bugs.Perform Functionality and Regression Testing. Experience in different phases of testingAnalyze the test requirements specifications.Good Communication and Analytical Skill.If you are interested, forward your CV to pagkis_testing_jobs@yahoo.com============ ========================================= ======
More About: Gent

Openings in Noida
2007-10-27 07:12:00
========================================= ==================Date: November 14, 2007There are some opening in Xansa, Noida . Below are job details:Position: Test Engineer/Test AnalystLocation: NoidaJob description: 3+ years of experience of functional and non functional testing. Excellent skills in test designing test planning, test data preparation, various testing techniques, test execution & defect management. Must be able write test approach,test plans and test summary report.Experience in test automation using Mercury / Rational testing tools.Excellent Comm and client facing skills.Experience in testing of various applications * client server / mainframe / web based / functional / non functional testing.Experience in SAP testing, Retail, Banking, Insurance domain.If you are interested, please send your updated CV at career.india@xansa.com=================== ========================================= ========================================= =================Date: October 26, 2007R...

Openings in Gurgaon
2007-10-25 14:43:00
========================================= ================== Date: November 12, 2007Requirement in Fidelity Gurgaon . Below are job details:Location: Gurgaon Experience: 2 yrs-6 yrsJob Description:Experience in working with QTP/ Unix.Experience in working on the tool - Test director / QUALITY CENTRE.Basic Shell/Perl Scripting.Ability to define positive and negative tests.Ability to map testing approach and test cases to requirements.Ability to communicate defects in detail with supporting documentation.Knowledge on financial domainFor more details please call : 9818303447/9811668721/9818904477/98101215 62 or 0124-4052855/4052856/4052347/4052348/4052 349/4052351/4052996/4052997 If you are interested, please send your updated CV at Chandan.sakhuja@mahindia.comPlease note: Mah India has positions with Fidelity Bangalore for Testing for 4-6 yrs and with BroadRidge Hyderabad for QTP/ System Testing for 3-6 yrs.===================================== ====================== ====================...

Openings in Delhi
2007-10-25 12:21:00
========================================= ==================Date: November 03, 2007There are some urgent requirements in IRIS Softwares. Below are the details:Job Description : Analyse the Test Requirements Specifications and contributes in developing the Test Strategy.Develops Test Scenarios. Periodically reviews the test cases developed and the test execution results. Desired Profile: Minimum 3 yrs of experience in testing.Engineering Graduate/MCA Must understand SDLC. Experience: 3 - 5Location: Delhi , Delhi/NCRIf you are interested, please email your requme at hr@irissoftware.comReference: QA======================================= ========================================= ======================================Dat e: November 03, 2007There are some urgent requirements in Infogain Corporation. Below are the details:Job Description : Good knowledge of testing Analyze the test requirements specifications.Develop Test cases.Design and implement automation test strategy.Analyze the test re...

Rapid Testing
2007-10-23 18:40:00
Rapid testing is the testing software faster than usual, without compromising on the standards of quality. It is the technique to test as thorough as reasonable within the constraints. This technique looks at testing as a process of heuristic inquiry and logically speaking it should be based on exploratory testing techniques. Although most projects undergo continuous testing, it does not usually produce the information required to deal with the situations where it is necessary to make an instantaneous assessment of the product's quality at a particular moment. In most cases the testing is scheduled for just prior to launch and conventional testing techniques often cannot be applied to software that is incomplete or subject to constant change. At times like these Rapid Testing can be used. The structure of rapid testing is built four components:PeopleIntegrated test processStatic Testing Dynamic TestingThere is a need for people who can handle the pressure of tight schedules. They n...
More About: Rapid

Load Runner - Interview Questions
2007-10-22 15:52:00
1. What is load testing?Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine weather it can handle peak usage periods. 2. What is Performance testing?Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions on the timing of a single transaction. 3. What is LoadRunner ?LoadRunner works by creating virtual users who take the place of real users operating client software, such as sending requests using the HTTP protocol to IIS or Apache web servers. Requests from many virtual user clients are generated by Load Generators in order to create a load on various servers under test these load generator agents are started and stopped by Mercury's Controller program. The Controller con...
More About: Questions , Interview

CSTE JUNE 17th 2006
2007-10-19 19:54:00
Objective Questions:1. A question on fit components. Which of the following contributes to fit. a. Data b. Structure c. People d. Rule e. All of the above 2. Reliability, timeliness, consistency are included in which component of fit a. Data b. Structure c. People d. Rule 3. Who will develop the test process for software development using new technology? a. Management b. Project team c. Auditor d. Tester and few more options 4. Which of the following are relatively complete acceptance criteria? a. Performance should increase b. Response time should be with in 10 sec Few more statements. 5. One question was on "Experienced people can be used as a tool for estimating the cost- Budgeting" 6. The communication type which is rarely emphasized a. Listening Few more options... 7. There were 2 questions on maturity level e.g which level enforces control for technology.8. There were 3 question on standard,...
More About: June

CSTE April 22nd 2006
2007-10-19 12:14:00
Objective Questions: 1. Which communication skill will be neglected by mosta. Readingb. Listeningc. Writing 2. Therapeutic listening isa. Sympathetic listeningb. Listening to pieces of information… 3. Which model demonstrates relation between 2 or more parameters of effort, duration or resource?a. Costb. Constraintc. Function Point 4. In which model expertise can be used to estimate cost a. Top-Downb. Expert Judgmentc. Bottom-Up 5. Two objective questions on responsibility like who is responsible in issuing IT policy, work policy etc. 6. Fit for use isa. Transcendentb. Product Basedc. User Basedd. Value Based 7. Re-Use of data is done in which type of testing (Similar type 2 questions on retesting and regression testing)a. Capture/Play backb. System Testingc. Regression Testingd. Integration Testing 8. one question each on configuration management / Change Management / Version Control.9. In Acceptance testing, which data is used. a. Test Casesb. Use Casec. Test Plan 10. In four co...
More About: April , April 2

CSTE September/December 2005
2007-10-18 15:14:00
CSTE Sept 17, 2005:Objective Paper1: Q1. Who defined the standards?A) ISOB) QAIAns. ISO Q2. Juran is famous forA) Quality ControlB) ManagementAns. Quality Control Q3. Which one is not Statistical Tool?A) Cause & effect GraphingB) StratificationC) Run ChartD) Regression AnalysisAns. Cause & effect Graphing Q4. Histogram refers toA) Bar ChartB) Run ChartC) ParetoAns. Bar Chart Q5. Who are there in External IT TEAM?A) Non DeveloperB) Customer/ User Q6. Which one is not Structural Testing? A) RegressionB) Parallelc) Acceptanced) StressAns. Acceptance Q7. Who is not part of Inspection?A) Prj ManagerB) Authorc) Moderatord) Readere) InspetorAns. Prj Manager Q8. Tester job is not toA) Report Defectb) Who entered the defect in systemAns. Who entered the defect in system Q9. Which one is not secondary role of testerA) Raising Issuesb) Instilling Confidencec) cts improving processd) Insighte) developer workAns. developer work Q10. Acceptance testing isA) White Boxb) Black boxc) White b...
More About: September , December

Mercury Quality Centre
2007-10-16 15:44:00
Mercury Quality Centre is a web-based test management tool. It gives you a centralized control over the entire testing life cycle. It gives an easy interface to manage and organize activities like Requirements coverage, Test Case Management, Test Execution Reporting, Defect Management, and Test Automation. All these activities are provided from a single tool, which is web-based and can be accessed from any where. Hence, making the task of the testers and managers easy.Mercury Quality Centre can be divided into two parts:Site Administrator Bin Quality Centre BinSite Administration Bin: It is the starting point for the usage of Mercury Quality Centre. This part is used for all the administrative activities. Password for site admin is defined during the installation so make sure that you remember the password during installation. From this part of Mercury Quality Centre, we generally do the following activities:Creating the projectsAssigning users to the projectsCreating specific roles...
More About: Mercury , Ality

Software Testing Metrics
2007-10-16 14:51:00
- Cost of finding a defect in testing (CFDT):Total effort spent on testing / defects found in testingNote: Total time spent on testing including time to create, review, rework, execute the test cases and record the defects. This should not include time spent in fixing the defects. - Test Case Adequacy: This defines the number of actual test cases created vs estimated test cases at the end of test case preparation phase. It is calculated as No: of actual test cases / No: of test cases estimated- Test Case Effectiveness: This defines the effectiveness of test cases which is measured in number of defects found in testing without using the test cases. It is calculated as No: of defects detected using test cases*100/Total no: of defects detected- Effort Variance: {(Actual Efforts-Estimated Efforts) /Estimated Efforts} *100- Schedule Variance:{(Actual Duration - Estimated Duration)/Estimated Duration} *100 - Schedule Slippage: Slippage is defined as the amount of time a task has been de...
More About: Software , Testing , Metrics

Functional Testing Vs Non-Functional Testing
2007-10-15 18:28:00
Functional Testing : Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.Functional Testing covers:Unit TestingSmoke testing / Sanity testingIntegration Testing (Top Down,Bottom up Testing)Interface & Usability TestingSystem TestingRegression TestingPre User Acceptance Testing(Alpha & Beta)User Acceptance TestingWhite Box & Black Box TestingGlobalization & LocalizationTestingNon-Functional Testing: Testing the application against client's and performance requirement. Non-Functioning testing is done based on the requirements and test scenarios defined by the client. Non-Functional Testing covers:Load and Performance TestingErgonomics TestingStress & Volume TestingCompatibility & Migration TestingData Conversion TestingSecurity / Penetration TestingOperational Readiness TestingInstallation Te...

Join Us and Keep Yourself Upto Date...
2007-10-15 16:10:00
1. Join us at Google Groups. Here you can post your queries, exchange your ideas, job related questions or job postings in your company...To join our Google Group, enter your email id here...or Visit this group2. You can also Subscribe to our Software Testing newsletter. You will not get any kind of spam. We will send you emails only for the updations in the blog. You will receive emails only after one week or two weeks. It is simple and easy...Enter your Email to Subscribe: Powered by: MessageBot3. Adding this blog to your favourites is also just one step ahead... Once you add this blog address to your favourites, you can easily open the blog. You do not need to remeber the complete address or retype the address in address bar.

Software Errors
2007-10-15 14:34:00
One common definition of a software error is a mismatch between the program and its specification. In other words, we can say, a software error is present in a program when the program does not do what its end user expects.Categories of Software Errors :User interface errors such as output errors or incorrect user messages.Function errorsHardware defectsIncorrect program versionRequirements errors Design errors Documentation errors Architecture errors Module interface errors Performance errors Boundary-related errors Logic errors such as calculation errors, State-based behavior errors, Communication errors, Program structure errors, such as control-flow errors. Most programmers are rather cavalier about controlling the quality of the software they write. They bang out some code, run it through some fairly obvious ad hoc tests, and if it seems okay, they’re done. While this approach may work all right for small, personal programs, it doesn’t cut the mustard for professional softw...

Test Efficiency Vs Test Effectiveness
2007-10-12 14:44:00
I've seen that many test engineers are confused with the understanding of Software Test Efficiency and Software Test Effectiveness. Below is the summary of what I understand from Efficiency and Effectiveness.Software Test Efficiency:- It is internal in the organization how much resources were consumed how much of these resources were utilized.- Software Test Efficiency is number of test cases executed divided by unit of time (generally per hour).- Test Efficiency test the amount of code and testing resources required by a program to perform a particular function.- Here are some formulas to calculate Software Test Efficiency (for different factors):Test efficiency = (total number of defects found in unit+integration+system) / (total number of defects found in unit+integration+system+User acceptance testing).Testing Efficiency = (No. of defects Resolved / Total No. of Defects Submitted)* 100 Software Test Effectiveness:- Software Test Effectiveness covers three aspects:How much the ...

Software Test Planning
2007-10-11 13:03:00
The quality of Software Test ing effort depends on the quality of quality of Software Testing Planning . Software Testing Planning is very critical and important part of Software Testing Process. Below are some questions and suggestions for Software Test Planning:- Have you planned for an overall testing schedule and the personnel required, and associated training requirements? - Have the test team members been given assignments? - Have you established test plans and test procedures for Module testingIntegration testingSystem testingAcceptance testing- Have you designed at least one black-box test case for each system function? - Have you designed test cases for verifying quality objectives/factors (e.g. reliability, maintainability, etc.)? - Have you designed test cases for verifying resource objectives? - Have you defined test cases for performance tests, boundary tests, and usability tests? - Have you designed test cases for stress tests (intentional attempts to break system)? - Ha...

Task-Based Software Testing
2007-10-10 13:14:00
Once in a Software Testing conference held in Banglore, India, the topic of discussion was "How to test software’s impact on a system’s mission effectiveness?"Mostly cutomers want systems that are: On-time, Within budget, That satisfy user requirements and Reliable.Latter two concerns (out of above four) can be refined into two broad objectives for operational testing: That a system’s performance satisfies its requirements as specified in the Operational Requirement Document and related documents.To identify any serious deficiencies in the system design that need correction before full rate production.Following the path from the system level to software two generic reasons for testing software are:Test for defects so they can be fixed - Debug TestingTest for confidence in the software - Operational TestingDebug testing is usually conducted using a combination of functional test techniques and structural test techniques. The goal is to locate defects in the most cost-effective...
More About: Task

Test Director
2007-10-07 20:31:00
It is a Global Test Management tool, the industry’s first global test management solution. It helps organizations deploy high-quality applications more quickly and effectively. It has four modules: RequirementsTest PlanTest LabDefectsThese modules are seamlessly integrated, allowing for a smooth information flow between various testing stages. The completely Web-enabled TestDire ctor supports high levels of communication and collaboration among distributed testing teams, driving a more effective, efficient global application-testing process. Web-based Site Administrator: The Site Administrator includes tabs for managing projects, adding users and defining user properties, monitoring connected users, monitoring licenses and monitoring TestDirector server information. Domain Management: TestDirector projects are now grouped by domain. A domain contains a group of related TestDirector projects, and assists you in organizing and managing a large number of projects. Enhanced Reports and...
More About: Rect

Top down Testing vs Bottom up Testing
2007-10-06 10:52:00
Top down Testing : In this approach testing is conducted from main module to sub module. if the sub module is not developed a temporary program called STUB is used for simulate the submodule.Advantages:Advantageous if major flaws occur toward the top of the program. Once the I/O functions are added, representation of test cases is easier. Early skeletal Program allows demonstrations and boosts morale. Disadvantages:Stub modules must be produced Stub Modules are often more complicated than they first appear to be. Before the I/O functions are added, representation of test cases in stubs can be difficult. Test conditions ma be impossible, or very difficult, to create. Observation of test output is more difficult. Allows one to think that design and testing can be overlapped. Induces one to defer completion of the testing of certain modules. Bottom up testing: In this approach testing is conducted from sub module to main module, if the main module is not developed a temporary program ca...

Usability Testing Lab
2007-10-05 20:55:00
In the usability lab, users are asked to perform a few tasks (functions) with the product being evaluated. There are the people who are actual users of the product. All their actions are directly observed and captured – video recorded for detailed analysis later. The lab is equipped to support the systematic observation and analysis of human-computer interaction. The lab has three sections: Test section Control section Observation section Test Section: Here, an actual or representative user interacts with the product. A camera records the user’s body language and hand movements on the keyboard, mouse and manuals. The screen interactions are captured live via a scan converter. Control Section: Here, a remote control unit is used to control the camera angle and zoom, ensuring that all data of interest is captured even if the user moves. Also, outputs from the camera and scan converter are monitored and mixed as required, using a video mixer. Observation section: Usability engineer...
More About: Testing , Sabi