Posts

Showing posts from October, 2013

How to Build a Test Case?

Image
How to Build a Test Case? Software testing training is definitely the best process for a novice learner to get a detailed idea of what actually is the testing process all about, how is it done and what are the requirements for conducting testing of software and much more. Software Testing is an important component of SDLC process and is very necessary to find out the reliability of the software in yielding the desired performance for user satisfaction. During the software testing training, the learners are given better understanding of how better software products can be given to the market through accurate testing methodologies and how to apply different strategies for variant software testing needs. One of the essential requirements for a testing process is the input which is defined as test case in software testing terminology. What is Test Case? Test case defines the set of test inputs and execution conditions that a tester adopts to exercise evaluation process on the softw

Beyond ISEB ISTQB-BCS: User Acceptance Testing (UAT) for Software Systems Part 2

Image
Beyond ISEB ISTQB-BCS: User Acceptance Testing (UAT) for Software Systems Part 2 Test Environment The test environment must be as similar to the production environment as possible. This is simple to accomplish when the application or system is installed on a user's computer but a little more difficult in a client server or hosted environment. The environment should have the same software, hardware, and network configuration as the production environment. The environment should have all the common or shared data from the production environment. It may be possible to simply port this data from QA to UAT. The UAT environment should also have sufficient privately owned data to enable testing. This may be done by selecting one customer to test on, or one product, and to port this data from the production environment where the new system replaces an existing one, or to create the data manually where a manual system is being replaced. Another approach is to simply port all the data i

Beyond ISEB ISTQB-BCS: User Acceptance Testing (UAT) for Software Systems Part 1

Image
 Beyond ISEB ISTQB-BCS: User Acceptance Testing (UAT) for Software Systems Part 1 This is the first part of a 2 part article on User Acceptance Testing (UAT) of software systems. It follows my previous articles on Quality Management topics. Up to this point no-one outside the development and QA teams have test driven your new software system. You've proven that there are no glitches in the software by thoroughly unit and function testing it, you've proven that it is well integrated with integration testing, and you've even proven that it meets the requirements specified for it (or at least the QA groups interpretation of those requirements), but you still haven't passed the ultimate test: do the users like the system? Customer acceptance is critical when building a commercial product and still important when building an in-house system. New software systems are usually introduced to replace existing systems that users have become accustomed to. Changing the way the

Beyond ISEB ISTQB-BCS: Quality Management & Software Testing Tools

Image
Beyond ISEB ISTQB-BCS: Quality Management & Software Testing Tools   We discussed how to plan quality activities in my last article in this Quality Management series, including how to plan test tool acquisitions. This article will expand on the theme of automated test tools, their impact on the project, and how to choose a set that is suitable to your project. This is not a consumer report on all the various tools available; once you have decided on the type of tools (if any) that suit your project, you should use your existing vendor selection process to choose the right vendor. I mentioned in my first article that the type of software being developed, and the development platform used, constrains the types of tools available to you. Other influences on your selection will be the budget available to purchase these tools, the degree of training necessary, and the applicability of the tools on future projects. You will need to consider all these factors before making your final

Beyond ISEB ISTQB-BCS: Enterprise Software Testing

Image
Beyond ISEB ISTQB-BCS: Enterprise Software Testing Nowadays many companies face new challenges while designing effective and efficient testing strategies for enterprise applications. Incomplete or flawed test data means inaccurate testing, which can lead to application failure and business disruption. The basic approaches to build test environments include cloning application production environments and writing custom extract programs. These testing methods can be labour intensive, error prone and costly. None of the client would like to risk losing customers, market share, brand equity or revenue by delivering applications that have not been thoroughly tested. For this reason, looking for a dedicated enterprise application testing company is a must. Ensuring Both End-User and System-Wide Quality for Enterprise Applications, dedicated performance testing companies, use industry leading tools to perform most complete and collaborative Enterprise Software Testing solutions. Mindfire

Beyond ISEB ISTQB-BCS: Top 20 Software Testing Practical Tips For the Workplace.

Image
Beyond ISEB ISTQB-BCS: Top 20 Software Testing Practical Tips For the Workplace. I hope all testers will browse these software testing sensible practices. Browse all points rigorously and inspect to implement them in your day-to-day QA activities. Usually this can be often what I expect from this article; if you are doing not understand any QA apply, rise for lots of clarification in comments below. After all, you may learn of those testing practices by experience. But then why not attempt to learn of those things before making any mistake? Since passing ISEB-ISTQB I've came across a variety of effective testing practices I learned from experience in the workplace: 1) Learn to analysis your results totally. Don't ignore the result. the last word take a glance at result might even be 'pass' or 'fail' but troubleshooting the inspiration reason behind 'fail' will lead you to the solution of the matter. Testers are revered if they not solely log the b