PagKis - Software Testing & Quality An execellent blog and online resource centre for Software Testing and quality assurance containing best of the best information for software testing and QA. See my daily posts on this blog and keep updated yourself with latest trends. Give your views also. Leave your comments... Happy Testing !! Statistics Unique Visitors: Total Unique Visitors: Outgoing: Total Outgoing: 16 0 15 1596

Articles from PagKis - Software Testing & Quality

Software Development Life-cycle 2008-01-02 23:33:00 SDLC is a systematic and orderly approach to solving problems related to software systems or in other words, we can say it is a structure imposed on the development of a software product.Domain Analysis: This phase is very important. The more knowledgeable you are about the domain, less the work required. Another objective of this phase is to make the analysts who will later try to elicit and gather the requirements from the area experts or professionals. So, this phase is an important prelude to extracting and gathering the requirements.Requirement Analysis: The most important task in creating a software product is extracting the requirements. Customers typically know what they want, but not what software should do, while incomplete, ambiguous or contradictory requirements are recognized by skilled and experienced software engineers.Scope Analysis: Once the requirements are gathered from the client, an analysis of the scope of the development should be determined and clearly stated. T ...

Solutions for the software development problems 2007-12-25 23:41:00 1. Requirements should be clear, complete, detailed, cohesive, attainable, testable and must be agreed by all players. Use prototypes to help nail down requirements. In 'agile'-type environments, continuous close coordination with customers/end-users is necessary. 2. Stick to initial requirements as much as possible. If changes are necessary, they should be adequately reflected in related schedule changes. If possible, work closely with customers to manage changes. This will provide them a higher comfort level with their requirements decisions and minimize excessive changes later on. 3. Allow realistic and enough time to plan, design, test, bug fix, re-test, change, and document in the given schedule.4. Make extensive use of group communication tools - groupware, wiki's, bug-tracking tools and change management tools, intranet capabilities, etc. Insure that information/documentation is available and up-to-date, promote teamwork and cooperation. Continuousally communicate with end-us ...

Test Specification 2007-12-04 21: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, inc ...

When requirements are changing continuously 2007-11-29 21: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 test ...

Software Testing Estimation Process 2007-11-23 04: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 estimation ...

Defect Removable Efficiency 2007-11-15 22: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 03: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. This ...

Regression Testing 2007-10-31 21: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. F ...

CSTE Sept 16th 2006 2007-10-29 05: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. ...

Openings in US / Singapore 2007-10-27 00: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 00:41:00 Coming Soon... !! ...

For Freshers 2007-10-27 00: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 00:19:00 ===========================================================We have Urgent 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=========================================================== ...

Openings in Noida 2007-10-27 00:12:00 ===========================================================Date: November 29, 2007There are some openings in CSC, Noida in Manual and Automated Testing. Following are the details:Exp. - 3 - 5 Yrs (Relevent in Testing)Education - Only Engineering (BE/B Tech) or Full time MCA can apply.Job Type - Permanent.If you are interested, please send your CV at syadav22@csc.com ======================================================================================================================Date: November 29, 2007There are some openings in Headstrong. Below are job details:Experience :- 2 to 5 yrs.Location :- NoidaContact Person :- Sandhya SinghInterested candidates please forward their CV's to sandhya.singh@headstrong.com======================================================================================================================Date: November 14, 2007There are some opening in Xansa, Noida. Below are job details:Position: Test Engineer/Test AnalystLocation: NoidaJob description: 3+ ye ...

Openings in Gurgaon 2007-10-25 07:43:00 =========================================================== Date: December 18, 2007Requirement inBinary Semantics Ltd, Gurgaon for Software Test Professionals having minimum experince of 2.5 years in Manual Testing. Below are the details:Position: Sr. S/W testing EngineerIf interested please send your updated resume in WORD format to ashu@binarysemantics.com with Subject Line having Reference ID: - BSL-A0555-ST with the following details:Current Organization:-Total exp.:-Exp. Manual Testing:-Current CTC:-Expected CTC:-Joining Time required:-=========================================================== =========================================================== Date: December 17, 2007Requirement in Opelin - HP for Software Test Professionals having minimum experince of 2 years. Below are the details:Education: B.Tech / MCASkill Sets:Creating Test Cases and ExecutionTested .Net-based window/web-client and server applicationsHands on with Performance, Usability, Compatibility, Integration t ...