SoftwareTestingFramework

Shipping quickly may ship some bugs possibly as tester may not test the product exhaustively. But as quality assurance testing expert we should make sure that no major and critical bug should escape. All the critical and important flow must be covered. For example we shipped a CD and did not test that it should be auto run then this is major escape. As long as there are major bugs exist in a product it should not be shipped from a tester point of view. Minor and small UI bugs can be left aside. We may categorically mention that the product is being shipped with these known bugs.

Software quality assurance and Testing is a vital activity for creating a software and to assure quality. Software quality drives reputation and customer satisfaction. We are in an era were the software industry understands how essential it is to perform Software quality assurance&testing in order to create a high quality product. It has already been proven that performing testing at an early stage helps improve quality of a product and makes it reliable. Early shipping of a newly developed product without a cycle of testing can lead to blunders as the software would consist innumerous bugs which could not have been caught by the developers. An example of a quick shipment of software with bugs is "Ariane 5 rocket crash" which took place in June 1996. An incorrect line of code was the cause of the crash which resulted in a huge loss of half a billion dollars. The bottom line here is that it is necessary to conduct certain rounds of testing of product before its shipment in market as it would lead to a productive performance and satisfied customers.

Release date of any product should be decided after getting in and out of application and the number resources available for design, development and QA testing. If anything among these are left out, we won’t get a decent output. Shipping it early would definitely lead to a bad product. There have been many examples of early delivery failure wherein QA was not given proper time to find quality bugs which led to customer dissatisfaction and the product failed to make an impact. One can therefore agree with this point that shipping quickly may ship bugs.

Well, some of you may differ and believe that there are various quality improvement processes which helps the QA to deliver Quality products, if such processes are followed by QA then they can not only deliver Quality products but also in less time.  On the other hand taking more time for QA does not promise the delivery of Quality Product. There are various factors such as complexity of the software, knowledge of tester, experience of tester, etc. that directly affects the Quality of product.

In most cases QA testing folks would agree that shipping quickly a product increases the chances of shipping bugs.  If you are delivering a product quickly without thorough testing that definitely it contain bugs. Testing will never be done in a hurry. For testing any software you should have proper documentation, proper vision of the product, proper knowledge of its functionalities, priorities distribution is clear only than you can test the product and ship them.

Author:

Knowledge Sharing Team at QA InfoTech is responsible for research on new tools & technologies for effective quality assurance testingacross all industry verticals. QA InfoTech (an ISO 9001:2008 & CMMI III certified) is one of the leading Quality assurance Testing Companies with five testing “Centers of Excellence” in the United States and India.  It offers end to end QA testing services.

Links:

https://plus.google.com/110881056047596544779/posts?hl=en

For effective design, creation, and implementation of automated tests, having an automated software testing framework is essential. In order to get a better understanding of the testing framework that matches your requirements, a guideline can really help in reaping several benefits. When designing an automation software testing framework, the primary thing you need to create is test scripts. These scripts explain the actions to be performed against every object, and are generally created for single actions that would be applicable in multiple scenarios. Although ensures a comprehensive result, it often leads to duplicate testing efforts as well.

To design a testing framework with reusable components, all you have to do is take into account certain elements that need to be incorporated. These include maintaining an objects repository, identifying the actions that have to be automated for each object of the software, compiling test results into a database and ensuring easy retrieval of data, checking the effectiveness of the device on which the software would run, managing error handlers and logs, and more. With these integrated, you have to design a framework that is easy to maintain and expand when required, and is capable of acting independently of the software being tested.

Once the designing phase is over, you have to develop the automation software testing framework with the help of some set tools that answer your automation needs. Using different scripting languages, the reusable components of your testing framework can be developed. Along with these, you would need driver and worker scripts that execute transactions for each test case that can be mapped to a group of test cases associated to a specific scenario, screen or window. Following this stage, comes the step of recognizing scheduler requirement where a batch script is set to run within a specific period of time. The advantage with this is every user gets to configure the scheduler and apply the test execution.

Cloud Testing requires cloud infrastructure for software testing. Organizations involved in testing face many challenges like limited test budget, meeting deadlines, high cost per test, large number of test cases or no re usability of test cases and geographical distribution of users enhance the challenges. Cloud Testing can solve these entire problems. The major problem behind testing in cloud network is performance, security and load testing, and using legacy tools it is difficult to do testing on this scale keeping in mind cost and complexity of testing. Testing a cloud application and network demands for a solution for application traffic and current security coverage and exceptional high performance and throughput. So first we need to create a realistic testing environment with a mix of applications and security attacks. In a cloud based network or scale it is always inefficient and costly to perform performance and load testing. The added dynamic of routine maintenance, patches and upgrades should be considered and there is a need to factor in the time to test how the patches and upgrades will impact performance. Very few options are available for vendors, most of which would erode the very value propositions that make cloud computing so attractive—cost savings and agility. So there is a need to enhance the testing tools to work in a well established cloud based testing network in order to get maximum benefit of this technique.

  Cloud Testing has a real challenges for testers nowadays.  As cloud usages are increasing day by day. Mobile operators are saving their data on cloud. As user can access their data from anywhere in data exist on the cloud. But cloud testing have also few issues for tester. Main issue with testing on cloud is complexity of testing, cost, application traffic and Security. For cloud testing firstly we need to establish testing environment on cloud for application. Performance and load testing are very difficult on cloud and also very costly.

  Cloud testing is the tipping point for the change in the QA testing industry, in the vast grown software industry, cloud computing has emerged as a new technology which penetrates the software industry. As in cloud testing which is also a type of software testing in which web applications use the cloud computing environment. Other reason is that nowadays cloud computing is not only used as an enterprise application which involves media, tele-communication ,financial services, retail etc but it is  also used by people to handle their data through mobile, because  mobile operators provide virtual spaces to their customers to opt for cloud computing. The only place where cloud testing fails is when we talk about security testing or load testing as it provides very limited option to do such types of testing for cloud based applications because in order to test the cloud based application we need high performance and a realistic environment

  Cloud computing has set a new bar for QA testing industry. There are many challenges to overcome after the introduction to cloud computing. The use of old legacy tools in cloud computing world. There are significant performance problems which arise out of high costs and complex environment of cloud computing. Legacy tools cannot cope with the changing environment of cloud computing applications. Testing at this level requires diversity in application traffic, high performance tools and sophisticated security. Performance and load testing in this evolving environment is very difficult and costly to achieve. Maintenance and timely upgrades also play a big role in QA Testing activities.

In order to evaluate the performance of the software in terms of responsiveness and stability, Performance Testing is done. Performance Testing also investigate and verify the others quality attributes of the system.There are various types of the Performance testing ie Load testing, Endurance, Spike, Configuration, Isolation and Stress Testing. It has following attributes:

·         It judge on the performance criteria.

·         It compares between the 2 and tells which is better.

·         It also tells us which part is responsible for the bad performance of the system.

·         It can be performed across the web and even in different parts of the country.