Programming Solution

This program takes input from two excel sheet and group into one sheet DEFINE VARIABLE cal AS DECIMAL FORMAT "->>>,999,999.999". DEFINE VARIABLE cal1 AS DECIMAL FORMAT "->>>,999,999.999". /*DEFINE VARIABLE site1 LIKE sct_site.*/ DEFINE STREAM tero. DEFINE TEMP-TABLE ttinv NO-UNDO FIELD tt_part AS CHARACTER FIELD tt_qty AS DECIMAL FORMAT "->>>,999,999.999" FIELD tt_val AS DECIMAL FORMAT "->>>,999,999.999". DEFINE TEMP-TABLE ttinv1 NO-UNDO FIELD tttt_part1 AS CHARACTER FIELD tttt_qty1 AS DECIMAL FORMAT "->>>,999,999.999" FIELD tttt_val1 AS DECIMAL FORMAT "->>>,999,999.999". INPUT FROM "C:\Documents and Settings\sachingaur\My Documents\gaur-27\pptrp07.csv". REPEAT: CREATE ttinv. IMPORT DELIMITER "," ttinv. END. INPUT CLOSE. INPUT FROM "C:\Documents and Settings\sachingaur\My

Sample program to export data of table in excel file lets assume we have a table name ferrari having fields tyre , mirror , seats , number. if you want to export the data of this table in excel write the following code output to "Ferrari.xls" . for each ferrari no-lock: put unformatted tyre "~011" mirror "~011" seats "~011" number "~011" skip. end. output close.

For more software testing articles visit: http://www.softwaretestinghelp.com Main features of unix : Multi user - More than one user can use the machine Multitasking - More than one program can be run at a time. Portability – This means the operating system can be easily converted to run on different browsers. Commands ls when invoked without any arguments, lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. Files whose names start with "." are not listed, unless the -a flag is specified or the files are specified explicitly. Without options, ls displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal

1) Functionality Testing 2) Usability testing 3) Interface testing 4) Compatibility testing 5) Performance testing 6) Security testing 1) Functionality Testing: Test for - all the links in web pages, database connection, forms used in the web pages for submitting or getting information from user, Cookie testing. Check all the links: * Test the outgoing links from all the pages from specific domain under test. * Test all internal links. * Test links jumping on the same pages. * Test links used to send the email to admin or other users from web pages. * Test to check if there are any orphan pages. * Lastly in link checking, check for broken links in all above-mentioned links. Test forms in all pages: Forms are the integral part of any web site. Forms are used to get information from users and to keep interaction with them. So what should be checked on these forms? * First check all the validations on each field. * Check for t

What is software testing? Software testing is more than just error detection; Testing software is operating the software under controlled conditions, to (1) verify that it behaves “as specified”; (2) to detect errors, and (3) to validate that what has been specified is what the user actually wanted. 1.Verification is the checking or testing of items, including software, for conformance and consistency by evaluating the results against pre-specified requirements. [Verification: Are we building the system right?] 2.Error Detection: Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn’t or things don’t happen when they should. 3.Validation looks at the system correctness – i.e. is the process of checking that what has been specified is what the user actually wanted. [Validation: Are we building the right system?] Testing is the process of analyzing a software item to detect the differences between existing and required cond

Learn to analyze your test results thoroughly. Do not ignore the test result. The final test result may be ‘pass’ or ‘fail’ but troubleshooting the root cause of ‘fail’ will lead you to the solution of the problem. Testers will be respected if they not only log the bugs but also provide solutions. Learn to maximize the test coverage every time you test any application. Though 100 percent test coverage might not be possible still you can always try to reach near it. To ensure maximum test coverage break your application under test (AUT) into smaller functional modules. Write test cases on such individual unit modules. Also if possible break these modules into smaller parts. E.g: Lets assume you have divided your website application in modules and ‘accepting user information’ is one of the modules. You can break this ‘User information’ screen into smaller parts for writing test cases: Parts like UI testing, security testing, functional testing of the ‘User information’ form etc. Ap

Following are some facts that can help you gain a better insight into the realities of Software Engineering. The best programmers are up to 28 times better than the worst programmers. New tools/techniques cause an initial LOSS of productivity/quality. The answer to a feasibility study is almost always “yes”. A May 2002 report prepared for the National Institute of Standards and Technologies (NIST)(1) estimates the annual cost of software defects in the United States as $59.5 billion. Reusable components are three times as hard to build. For every 25% increase in problem complexity, there is a 100% increase in solution complexity. 80% of software work is intellectual. A fair amount of it is creative. Little of it is clerical. Requirements errors are the most expensive to fix during production. Missing requirements are the hardest requirement errors to correct. Error-removal is the most time-consuming phase of the life cycle. Software is usually tested at best at the 55-60% (

Certification Information for Software QA and Test Engineers CSQE - ASQ (American Society for Quality)’s program for CSQE (Certified Software Quality Engineer) - information on requirements, outline of required 'Body of Knowledge', listing of study references and more. CSQA/CSTE - QAI (Quality Assurance Institute)'s program for CSQA (Certified Software Quality Analyst) and CSTE (Certified Software Test Engineer) certifications. ISEB Software Testing Certifications - The British Computer Society maintains a program of 2 levels of certifications - ISEB Foundation Certificate, Practitioner Certificate. ISTQB Certified Tester - The International Software Testing Qualifications Board is a part of the European Organization for Quality - Software Group, based in Germany. The certifications are based on experience, a training course and test. Two levels are available: Foundation and Advanced.

ISO - International Organization for Standardization is a network of the national standards institutes of 150 countries, on the basis of one member per country, with a Central Secretariat in Geneva, Switzerland, that coordinates the system. ISO is a non-governmental organization. ISO has developed over 13, 000 International Standards on a variety of subjects.

Six Sigma is a quality management program to achieve "six sigma" levels of quality. It was pioneered by Motorola in the mid-1980s and has spread to many other manufacturing companies, notably General Electric Corporation (GE). Six Sigma is a rigorous and disciplined methodology that uses data and statistical analysis to measure and improve a company's operational performance by identifying and eliminating "defects" from manufacturing to transactional and from product to service. Commonly defined as 3.4 defects per million opportunities, Six Sigma can be defined and understood at three distinct levels: metric, methodology and philosophy... Training Sigma processes are executed by Six Sigma Green Belts and Six Sigma Black Belts, and are overseen by Six Sigma Master Black Belts.

Developed by the software community in 1986 with leadership from the SEI. The CMM describes the principles and practices underlying software process maturity. It is intended to help software organizations improve the maturity of their software processes in terms of an evolutionary path from ad hoc, chaotic processes to mature, disciplined software processes. The focus is on identifying key process areas and the exemplary practices that may comprise a disciplined software process. What makes up the CMM?  The CMM is organized into five maturity levels: Initial Repeatable Defined Manageable Optimizing Except for Level 1, each maturity level decomposes into several key process areas that indicate the areas an organization should focus on to improve its software process. Level 1 Initial Level:  Disciplined process, Standard, Consistent process, Predictable process, Continuously Improving process Level 2 Repeatable: Key practice areas - Requirements management, Software project plan

Buying the Wrong Tool Inadequate Test Team Organization Lack of Management Support Incomplete Coverage of Test Types by the selected tool Inadequate Tool Training Difficulty using the tool Lack of a Basic Test Process or Understanding of What to Test Lack of Configuration Management Processes Lack of Tool Compatibility and Interoperability Lack of Tool Availability

Take time to define the tool requirements in terms of technology, process, applications, people skills, and organization. During tool evaluation, prioritize which test types are the most critical to your success and judge the candidate tools on those criteria. Understand the tools and their trade-offs. You may need to use a multi-tool solution to get higher levels of test-type coverage. For example, you will need to combine the capture/play-back tool with a load-test tool to cover your performance test cases. Involve potential users in the definition of tool requirements and evaluation criteria. Build an evaluation scorecard to compare each tool's performance against a common set of criteria. Rank the criteria in terms of relative importance to the organization.

There are three broad options in Test Automation: Full Manual Partial Automation Full Automation Reliance on manual testing Redundancy possible but requires duplication of effort Reliance on automated testing Responsive and flexible Flexible Relatively inflexible Inconsistent Consistent Very consistent Required for automation - - Low implementation cost - High implementation cost Low skill requirements - High skill requirements High repetitive cost Automates repetitive tasks and high return tasks Economies of scale in repetition, regression etc Fully manual testing has the benefit of being relatively cheap and effective. But as quality of the product improves the additional cost for finding further bugs becomes more expensive. Large scale manual testing also implies large scale testing teams with the related costs of space, overhead and infrastructure. Manual testing is also far more responsive and flexible than automated testing but is pro

Let’s first look at some common relationship problems and why many romantic partnerships do not work out. 1. Ego, Fear, & Emotional Insecurities As with material possessions or professional achievements, relationships give our ego a method by which to identify who we are to the outside world. The problem is that we attach so much of our identity to the external appearance of our relationships that we lose touch with the parts of ourselves that are wise and conscious. The attachment to this false identity leads to a feeling of desperation rather than fulfillment. After all, without the relationship, or the job, or whichever other false identity we have chosen, who would we be? Besides the ego identification, it’s easy to develop a dependency on companionship. That independent person that we once were starts to evaporate. Our mind becomes fogged and as our self-identification begins to attach itself to the other person, unconsciously or consciously, we become afraid to lose that

Automating testing is no different from a programmer using a coding language to write programs to automate any manual process. One of the problems with testing large systems is that it can go beyond the scope of small test teams. Because only a small number of testers are available the coverage and depth of testing provided are inadequate for the task at hand. Expanding the test team beyond a certain size also becomes problematic with increase in work over head. Feasible way to avoid this without introducing a loss of quality is through appropriate use of tools that can expand individual’s capacity enormously while maintaining the focus (depth) of testing upon the critical elements. Consider the following factors that help determine the use of automated testing tools: • Examine your current testing process and determine where it needs to be adjusted for using automated test tools. • Be prepared to make changes in the current ways you perform testing. • Involve people who will be

The documents outlined in the IEEE Standard of Software Test Documentation covers test planning, test specification, and test reporting. Test reporting covers four document types: 1. A Test Item Transmittal Report identifies the test items being transmitted for testing from the development to the testing group in the event that a formal beginning of test execution is desired Details to be included in the report - Purpose, Outline, Transmittal-Report Identifier, Transmitted Items, Location, Status, and Approvals. 2. Test Log is used by the test team to record what occurred during test execution Details to be included in the report - Purpose, Outline, Test-Log Identifier, Description, Activity and Event Entries, Execution Description, Procedure Results, Environmental Information, Anomalous Events, Incident-Report Identifiers 3. Test Incident report describes any event that occurs during the test execution that requires further investigation.Details to be included in the repor

1. Forget and forgive This is the most powerful aid to peace of mind. We often nurture ill feeling inside our heart for the person who insults or harms us. We forget that the insult or injury was done to us once but by nourishing the grievance we go on excavating the wound forever. Therefore it is essential that we cultivate the art of forgiving and forgetting. Believe in the justice of God and the doctrine of Karma. Let Him judge the act of the one who insulted you. Life is too short to waste in such trifles. Forget, forgive, and march on. 2. Do not interfere in others' business Most of us create our own problems by interfering too often in others' affairs. We do so because somehow we have convinced ourselves that our way is the best way, our logic is the perfect logic, and those who do not conform to our thinking must be criticized and steered to the right direction, our direction. This kind of attitude on our part denies the existen