Thursday, March 19, 2020

Quality Assurance Software Testing


Quality assurance software testing services is an essential part of any software development project. It is the responsibility of software developers and testers to make sure that the newly developed software programs are reliable, consistent, functional, accurate, secured, compatible and accurate. 

According to research, nearly three fourth of software projects are either late, or are over budget or are cancelled before being completed. Software testing is the process of measuring the quality of a developed computer software program. The software should be complete, correct and secured, portable, efficient, maintained, reliable and usable. Testing is a process intended to find errors in a newly designed software program. People who are engaged in test automation reduce costs, relieve resources and achieve the product goals of their group.

With increasing number of software programs being released annually, there is need for software testing and every aspect of the software program must be validated and good-quality. In automated software testing methods, tests are easy to generate, uphold and recycle. Quality assurance services software testing confronts the assumptions, uncertainties and risks involved in a software program. A software test looks if there are any defects in the software program and if the software program is working as expected.

Assurance software testing should be started at an early stage of software development. With each implementation, the software program should be tested, and as a result, the program is ready for release much earlier.

Each software testing method has a different method of testing and is undergone with a different objective. They can look for errors, quality, safety, faultlessness, protection, potentiality, maintainability and other aspects of a software program. A software program is incomplete without proper testing.

Before testing a software program, a test plan is prepared which includes the tools to be used, various inputs and the expected results. Code review is also a part of Assurance software testing and is done by a programmer who has the basic knowledge about coding. Code review contains the comments before a code block begins and the proper arrangement of coding. 

A favourable code in a review of software testing will ensure that the software programme is easily maintainable.
Assurance software testing service providers is done by running a test through the system under various circumstances and configurations. It validates the behaviour of the program being tested. First of all, the features of the program to be tested are listed. Then the test programs that will be needed to be run are planned, created and modified. Then these tests are executed to the program. 

The results are then evaluated and reviewed. Reuse of the tests improves its development and automation aims at the execution portion of the test. Some components of software testing are remote monitoring, resource management, data management, synchronization, file transfer, logging, etc.

Over the last two decades, software development industry has been under pressure to develop more and more high-quality software programs. The tester should know which automated tools are available for testing, and how to choose the right ones for the current project.

Conclusion

Hope these are the important and valuable software testing services which could be followed by any vendors. And your thoughts and suggestions are welcome through comments. And hereby the Qa Services resides with perfect solutions and techniques desired by leading and innovative techniques.

Thanks and Regards,
Zeppelin
Indium Software- software testing companies

Ensure The Efficiency Of Software By Software Testing


Software testing is a process of testing the software that has been developed before launching it in the market. Testing becomes essential in order to give a final approval to the software. If there is even a slight fault in the programming, then the whole software is considered as failed. Software testing is not done to fix up some left out program in the software or correct some data in it. Instead, it is done to check whether it is a success or a failure. 

In any other hardware designing, the faults or the deficiencies can be improved or a new part can be installed but the faults and deficiencies of the software gets embedded in it and becomes latent only when it is activated by the user. So, testing is an essential requirement for any software.

Computer Software is a set of computer programs that are used to run the computer system. There have to be corrected and modified before final approval. It is not like a hardware that gets corroded or breaks or cracks while adjusting or packing and can be fixed or replaced.

So, software testing enables you to check the technical requirements that have been of the software. Software testing gives a sense of completion and perfection. Summing it up, you can say that software testing companies can be done for evaluating or analyzing the capacity of the software to execute its intended function. 

If the software is launched without being tested, it will certainly affect the company reputation in the information technology market and in such cases, nothing gets retrieved since there is great competition in the IT field. There are several companies who are designing and manufacturing the latest software technology to beat the older ones and to bring about more development in each and every sphere of human life.

Software is tested on the basis of technical requirements too described under ISO standard ISO 9126 like capability, reliability, efficiency, portability, maintainability, compatibility and usability.

The main aim of software testing services is to find software bugs as soon as possible and debug the software. Software bug is a mistake or fault in a computer program that stops the software from executing its projected function. These bugs arise due to the mistakes in source code or design of the software program. 

Source code is a set of files that converts the form of human readable data in to computer- programming language. A report is made depicting the details of the bugs present in the software. If there are numerous bugs in a program then it is called buggy. It is really important to check out and correct these bugs before the launch of the software since once activated in the user computer, they infect the programming of the whole system.

There are various types of software testing. Some of the important ones are enlisted below:

1. Black box testing
2. White box testing
3. Unit testing
4. Incremental integration testing
5. Integration testing
6. Functional testing
7. System testing
8. End-to-end software testing
9. Sanity testing
10. Compatibility testing
11. Comparison testing
12. Alpha testing
13. Beta testing
Conclusion

Hope these are the important and valuable software testing services which could be followed by any vendors. And your thoughts and suggestions are welcome through comments. And hereby the Qa Services resides with perfect solutions and techniques desired by leading and innovative techniques.

Thanks and Regards,
Zeppelin

Thursday, December 26, 2019

Quality is inversely proportional to variability

As this is my first post on this new Blog (more coming soon),  I will deal with one of my favourite subjects :–

Trying to apply Statistical Process Control methods to the process improvement of software production and maintenance.

There are many perspectives and definitions of quailty that speak to the pioneering Statistical Process Control work that W. Edwards Deming and others did in post war Japan to rebuild its depleted manufacturing capability.

 A more recent and succinct definition of quality comes from Douglas C. Montgomery – 1996 and is:-

 Quality is inversely proportional to variability

 This quote is taken from his book entitled:-

 Introduction to Statistical Quality Control: Student Resource Manual

 Whilst this book is still on my reading list the overall notion that quality improvement can be seen as a reduction of variability in process and products got me thinking about how variability is addressed in the various Project related process areas of CMMi (The Software Engineering Institute’s, Software Process Improvement framework).

 General issues with applying Statistical Quality Control methods to Software production:-

 The basic idea of any process improvement initative is to characterize the current state of production, together with the value and cost of what is produced, with the intention to alter the given process in such a way that the value increases andor the cost decreases.

The issue with software production (achieved under projects) is that the processes and their outputs are highly variable when compared to their manufactured counterparts. This raises issues of comparing like for like when trying to form hypothesises for potential improvements or verifying that any change has in fact made an improvement.

 How project management variation is addressed in CMMi

 The CMMi for software development, a software process improvement framework, breaks down the various components of Project Management and recommends a configurable (mix and match) approach to selecting an appropriate project lifecycle.

By making the whole project management process configurable for various predefined lifecycles, what can be achieved with CMMi is an isolation of those processes (procedures) that are consistent over time and therefore more readily subjected to traditional process improvement methods and techniques.

 Here is a look at how CMMi splits up the components of project management and how this separation allows for an identification of consistency that will lend itself to Statistical Quality Control.

 The Organizational Process Definition (OPD) process area.

 Within CMMi the goals (remembering CMMi specifies What is required and not How to do it) of the OPD are concerned with creating a Process Asset Library (PAL).

 The PAL documents all the processes that are to be followed and subjected to measurement for improvement. These processes include various project life cycle models e.g.

Waterfall
Spiral
Evolutionary
Iterative

In this way there are multiple lifecycle models defined and the appropriate one is chosen for a given project.

 The PAL would also document smaller tasks such as Usability Testing so that during Project Planning the appropriate Project lifecycle would be selected in addition to mixing and matching the various tasks within the selected project lifecycle.

 This project lifecycle configurability allows for similar tasks to be compared over the course of multiple projects. For example the Usability testing task would remain stable and be applied equally to an iterative or waterfall project lifecycle.

 CMMi has a Quantitative Project Management (QPM) process area that also makes use of this modular structure. By recording metrics for the previous performance of standard (modular) tasks, performance and quality objectives can be established for the given project in order to plan and monitor the project’s progress.

 In essence CMMi allows for a project’s structure to be assembled from tasks and processes defined in the PAL. Each individual component in the PAL also has documented performance metrics which can be used for Quantitative Project Management to monitor and react to performance testing services or quality issues.

 This modular approach to breaking down project tasks with associated performance metrics will ultimately reduce variability in the process, which in turn will facilitate a process improvement initiative.

 Although project management is given as an example the question we should all ask, as quality engineers, is what processes (or parts of processes) will be consistent over multiple projects and how can that consistency be leveraged for process measurement and improvement.

The pragmatic difference between Verification and Validation

There are many definitions of the terms Verification and Validation on the web and in essence they all come down to the objectives and goals of the undertaking, rather than any given methods or techniques applied.

The typical definitions for the V&V terms are:-

Verification: Determining if the software product is being built correctly

Validation: Determining if the correct software product is being built.

Although these terms look similar and are both concerned with providing the right product at the optimal cost, each of these process areas serves a different purpose.

Validation speaks to the overall value of the delivered product, when placed in its working environment whilst verification speaks to the correct procedures and standards, to deliver the product, being followed. Ironically a product may be verified to have followed the correct procedures but invalid in that ultimately it did not fulfill its intended purpose when placed in the production environment.

A typical SDLC with Validation and Verification activities.

For further clarification consider the typical SDLC as a reference point for verification and validation activities.

Business requirements are the main focus of validation both in terms of inspection and testing the delivered application. In terms of inspection (of the business requirements) the question “will this satisfy the business need when implemented” is one that is addressed.

 There is also a verification dimension to an inspection (or walk-through) of the business requirement that is concerned with the correct standards or format being used for the business requirements document. In this way the verification of the business requirements can be done by someone who does not know the business needs but rather knows the correct structure for the requirements document itself.

Following on to the technical specification that has been derived from the business requirements we can see that a similar certification exercise can be performed in that the document can be verified to meet standards.

The question of validation of the technical specification is more complicated. If validation of the technical specification is to be done it must be done by someone who knows the intended purpose of the software.

If there is a traceability exercise done, i.e. someone checks that each paragraph in the business requirements has an entry in the technical specification, then this is not strictly a validation activity.

The process of requirements traceability, as noted in the previous sentence, is part of verification. If there is some walkthrough of the technical specification, with potential screen shots and mock ups, with the business proponents then a validation activity could take place.

As we move to the developed software product it is possible for further validation activities to take place but these will require either a prototype or some other view of the software that is visible to the business proponents.

One of the reasons small iterations (agile style) have become popular is that validation can be done incrementally rather than waiting for the final product to be completed.

When the system has been developed the testing of the system against the technical specifications is a verification activity whilst the testing of the software against the business requirements is a validation activity.

Through all stages of the development cycle any review of the software (or specifications) that answers the fundamental question of ‘will this product fulfill its business purpose?’ is considered validation.

Validation should be done as early as possible in the development life cycle, in order to avoid late surprises that the software is not what the end user (or customer) required. Many software projects have followed the prescribed standards and procedures but have failed due to producing an ‘invalid’ product.

The consequences, for the Quality assurance and software testing services team’s organizational structure, of these definitions will depend on the complexity of the business problem being addressed.

If the business problem is trivial then the business and systems analysis together with validation and verification activities can be combined.

Generally it is more useful to separate out the duties of developers from testers, so that so called independent verification and validation (IV&V) can be carried out.

Strictly speaking the term independent verification and validation refers to a completely separate team (outside of the developer management structure) being engaged to conduct the IV&V activities.

That said there is no issue combining the actual V&V activities, so that someone may perform both system and business requirements testing. The acceptance testing should still be done by a business proponent as the main function of acceptance testing is the final approval.

Learn more about performance testing services

Where the business problem is complicated, and in most large companies the problem is complex due to the many interconnecting systems, then a separation of validation from verification, in terms of personnel, is both effective and efficient.

In terms of effectiveness, having individuals (typically business analysts) focus on the definition then subsequent testing (validation) of the requirements will create the channel by which the Voice of the Customer (VOC) can be heard throughout the software delivery process.

Business Process Management (BPM) and other business facing modeling techniques are effective communication artifacts that specialized business analysts can acquire and build skills in. In this way (specialization around validation activities) a professional team of business proponents can be established and developed.

The methods and techniques used for verification are considered more technical in orientation (than business facing validation techniques).

 Having more technical team members specialize in verification activities will yield efficiency and effectiveness gains. Consider white box testing techniques, which require code coverage to be measured, as a quality control activity that does not require any knowledge of the business requirements.

Such an activity is a prime example of software verification, in that a high percentage of code coverage can be ‘specified’ as a requirement of testing. In this way having a high percentage of code covered gives a ‘yes’ answer to the question “Are we building this product correctly?”. The application of white box testing techniques is better served by having personnel specialize in those particular (more technical) skills.

Conclusion.

Separating team members into verification of validation activities, for large complex projects, is an effective divide and conquer strategy for breaking down the overall software quality control goals.

By recognizing the essential differences between verification and validation an organization is better positioned to engage in meaningful process improvement as personnel develop the required skills and techniques in these two process areas.

Selenium Webdriver and Jmeter testing tools should always be on your radar

Over the past 3 or 4 years I have noticed two open source software testing services tools mature into a must have for any testers personal tool box. These two basic tools (Selenium Webdriver and Jmeter) are continually evolving in terms of their widespread use and the functionality offered.

 Although I am sure most readers here will have heard of them, I believe that they are always worth revisiting as they evolve in line with the software that they are testing evolves.

Selenium (Webdriver)

For Web browser automated testing services, this open source tool has become the industry standard. Many QA departments are now favoring this mature testing tool over the commercial offerings. Its popularity is due to a combination of a wide spread talent pool (for employers to utilize) as well as many great articles and add-ons that its loyal followers have produced.

Tips:-

Install Firebug (or other DOM inspector) to determine how a given element can be accessed.

Establish a framework that facilitates reuse, such as Page Objects

Use the Java version of WebDriver, there are many complimentary frameworks written in Java: JDBC, JUNIT, TESTNG etc. and there are also numerous Java examples of implementing Webdriver in Java.

Jmeter

Just as Selenium Webdriver has become the standard for automated Web browser testing Jmeter has become the open source standard for performance testing services.

Although Jmeter is considered a leader in the open source arena it is not as dominant as Selenium Webdriver when compared with the overall market (including commercial tools). Part of the reason why Jmeter is not as popular as commercial load testing tools is lack of ease of use.

That said, if you can invest a little of your time into understanding the basic Jmeter architecture, it will provide you with a useful load testing tool (and not just for the web but Databases, SOAP and email can all be tested with Jmeter).

Tips

Become familiar with a good network protocol analyzer (such as Fiddler) so you can understand your web traffic and its re-construction when using Jmeter).

Use the Plug Ins from Google which are ever growing and now include a REST sampler, JSON to XML converter and the useful server side metrics collection agents.

If you have looked at these tools in the past (especially over 3 years ago) and you are not using them, I would strongly recommend a second look.

Selenium Webdriver data driven page objects using java hash maps

There are many articles on the web about Webdriver frameworks that encourage a data driven approach to test case development. By separating the data from the executable code two benefits are realized, the first is that the test case can be reused in various scenarios: for example the ‘log on’ could be for an admin user or the chief purchasing officer by varying the name and password in the data parameters.

The second, not so obvious benefit, is that the data itself can be separately maintained and updated as required, this approach towards data maintenance is similar to making everything configurable in the application code itself.

For example if there was an implementation of a drop down option list that contained various shipping rates then by separating the list of rates and feeding them into the test cases, the list could be easily changed when the requirements changed.

One caveat to the above mentioned benefits of separating out data from the test case code is: Do not be tempted to validate from the same data source as what is used in the application.

This approach is tempting but the validation should be done from an independent source of data otherwise the application becomes self validating. That said it is valid to seed test data from values in the test database, just do not seed the verification data.

Hash maps are an ideal java structure for data driving your tests, whether you are using Webdriver or some other java based automation testing services framework.

To use hash maps you need the following package import:-

import java.util.HashMap;

The hash map can be thought of as a list of key and value pairs. Although this is a simplistic description, and I would encourage you to Google hash maps to find out more, the value of hash maps for data driving automated tests can be illustrated using this simple analogy.

The data type of both that Key and the Value can be defined when the hash map is created:-

HashMap wordcount = new HashMap();

Within an automated testing framework the hash map can be seeded (from a CSV file, DB or other data source) within the test runner or scenario you are driving the tests from.

Seeding the hash map from a data source is a matter of reading through the data source and loading the hash map. In this way the data file (or other source) is easily maintained should the requirements change.

There are many good examples of doing this, on the web. Just Google reading a CSV file into a hash map and you will get some useful articles.

Having seeded the hash map a page object can be called with the hash map as a parameter. The page object is a reusable function that is targeted at a given screen (page), for example the Log On page.

Within the page object, which contains all the Webdriver locators and code to set the values of the various elements, the hash map value pairs can be used to retrieve the key (data field) and the value that is to be set – e.g. (username, “Mike Smith) and (password, “mikes password”).

There are many examples on the web of how to retrieve specific Key values from the hash map, so I won’t repeat them but I will emphasize the additional benefits of using this construct.

If you want to make your page object flexible you could have a series of If statements, for each Key (data field) and If that Key exists (in the hash map) it is populated otherwise that field is left empty. In this way a specific number of fields (with their unique values) can be set in the page object, which could then be used in multiple scenarios.

In the simple Log on example you could just send the username to the Page object and the password could be omitted.

 If you did this then, to test the validation, that the system returns password required should be done outside of the Log On page object as the page object does not validate (as it only repeats the required steps). See the page object framework for more details of this approach.

Although this Blog post has only just touched on the use of hash maps for passing data variables into selenium Webdriver test cases (which could be organized as page objects), I hope I have conveyed the overall flexibility and advantages of using this versatile construct.

Using Mock objects in load testing

Introduction

One of the main problems with performance testing services is the overall scope and in particular applying scrutiny to an individual software component.

The first issue with scope is that if multiple components are being tested, as in a full systems performance test, it is difficult to isolate the system resources used by a given component (process). By way of example consider a Web services architecture that has Common Gateway Interfaces CGI (or asp and jsp etc) running on the same server.

When load is put on the front end (Web browser) the Web Services are called via the CGI and the resource utilization is an aggregate of both the CGI and the other Web services. This issue does go away if the components are separated out onto different servers but in most cases some shared server resource, by components, will exist.

The second issue, concerning scope, with performance testing a system, is that the complete system has to be built before a complete test can be executed through the front end (i.e. Web Service, CGI or Web Browser).

In the case of Web services both the client (usually Web browser, CGI, asp, jsp etc) and the backend data base need to be available to perform the end-to-end performance test.

Both of the issues of scope for performance testing can be addressed with mock services (stubs) and a test harness to drive the load from.

Mock Web Services.

Mock Web services are place holders for any SOA request that has to be developed. Mock services are similar to Mock objects for unit testing . There are many papers on Mock Objects, in the software testing services directory, that go into further detail.

The advantages of mock services for load testing are:-

The called service does not have to be fully complete.
The calling component (i.e. Web service) can be isolated in terms of measuring performance.
It is also easier to control the behavior of the returned values, using a Mock service, as these (canned) returned values can be defined for the given purpose.

It is important to note that this test is not a system test and other functional tests will need to be performed to validate the component but for the purposes of performance testing the mock object will be able to ‘stand in’ for the real thing.

An open source Mock service tool.

SoapUI has a web service mocking feature that allows for quick and easy building of mock services. This tool set also includes building the various responses that the anticipated calling program expects from the complete delivered web service.

The harness or driver.

Given we can isolate the server component from the Web Services; we now look to isolate that component from the client. This isolation is needed in any event in order to recreate large volumes of simulated service calls to the component under test.

If the component under test is itself a Web service then a SOAP load testing tool can be used as the driving harness.

If the component is a CGI (or other web server side component) a HTTP load driver can be used to put load on the component under test.

In either case a suitable open source load testing tool can be found.

Measuring the component under test.

When isolated there are a number of useful monitoring tools that can be used to measure the performance of the given component.

Although CPU is a useful measure to determine the overall performance of a middleware component it is essential to establish that a server side component is not leaking memory or not returning other unused resources (such as threads) back to the pool when appropriate. The first type of load test that should be performed on a middleware component, and this can be done early in the SDLC with Mock services, is stability testing.

With stability testing the memory, thread pool and CPU are monitored over an extended period, about six hours, of consistent load to determine if performance degrades over time.