Testing | Quality Assurance Services :AuxinSystems

Multivariate testing

2010-02-18T08:26:00.000-08:00

Multivariate testing is a process by which more than one component of a website may be tested in a live environment. It can be thought of in simple terms as numerous A/B tests performed on one page at the same time. A/B tests are usually performed to determine the better of two content variations, multivariate testing can theoretically test the effectiveness of limitless combinations. The only limits on the number of combinations and the number of variables in a multivariate test are the amount of time it will take to get a statistically valid sample of visitors and computational power.

Multivariate testing is usually employed in order to ascertain which content or creative variation produces the best improvement in the defined goals of a website, whether that be user registrations or successful completion of a checkout process (that is, conversion rate). Dramatic increases can be seen through testing different copy text, form layouts and even landing page images and background colours. However, not all elements produce the same increase in conversions, and by looking at the results from different tests, it is possible to identify those elements that consistently tend to produce the greatest increase in conversions.

Testing can be carried out on a dynamically generated website by setting up the server to display the different variations of content in equal proportions to incoming visitors. Statistics on how each visitor went on to behave after seeing the content under test must then be gathered and presented. Outsourced services can also be used to provide multivariate testing on websites with minor changes to page coding. These services insert their content to predefined areas of a site and monitor user behavior.

In a nutshell, multivariate testing can be seen as allowing website visitors to vote with their clicks for which content they prefer and will stand the most chance of them proceeding to a defined goal. The testing is transparent to the visitor with all commercial solutions capable of ensuring that each visitor is shown the same content on every visit.

System Test - Capacity Testing

2010-02-07T08:47:00.000-08:00

Scheduling Capacity Testing
Performance Test and Stress/Load Test occur during System Test or when enough of the application has been delivered. The earlier capacity testing can be applied, the earlier defects can be detected and mediated. It is critical to detect capacity related defects early because these types of defects often require architectural changes to the system. Because these tests usually depend on functional interfaces, it may be wise to delay until function testing has demonstrated some predefined level of reliability. A balance must be struck between testing early and testing when appropriate.

Designing Capacity Tests
Lack of capacity testing requirements and goals is one of the most common errors made during any capacity testing exercise. Test organizations will often go through the process of capacity testing only to discover the testing results do not present the project with any useful information. The solution is to treat Performance and Stress/Load testing the same as any other testing effort. The test organization needs to perform: Test Planning, Partitioning / Functional Decomposition, Requirements Definition / Verification, Test Case Design, Traceability (Traceability Matrix), Test Case Execution, Defect Management, and Coverage Analysis (for more on this see "Requirements based Function Test").

Implementing Capacity Tests
Both Performance and Stress/Load testing require a toolset that can put the system under a known load and measure the performance of the application while under load. Several shops have developed their own in-shop solutions for capacity testing and there are several capacity testing freeware, shareware, and commercial products available to meet this need. It is easy to fall into the .over-engineering. trap when implementing a capacity testing toolset - to avoid this trap ensure the solution meets the test organizations goals and that the toolset does not become a "goal" in itself.

Software QA and Testing Less-Frequently-Asked-Questions

2010-01-31T08:55:00.000-08:00

Why is it often hard for organizations to get serious about quality assurance?
Who is responsible for risk management?
Who should decide when software is ready to be released?
What can be done if requirements are changing continuously?
What if the application has functionality that wasn't in the requirements?
How can QA processes be implemented without reducing productivity?
What if an organization is growing so fast that fixed QA processes are impossible?
Will automated testing tools make testing easier?
What's the best way to choose a test automation tool?
How can it be determined if a test environment is appropriate?
What's the best approach to software test estimation?

what is defect life cycle?

2010-01-24T09:54:00.001-08:00

The defect life cycle is:
first when the defect is found it is made note of. (this is called the New stage)
Then it is sent to the developer (this is called the Open stage)
Once the developer fixes and sends back to the tester (it is called as Fixed)
Now the tester checks if the bug had been fixed , if it is fixed (it is called Closed)

if the bug is not fixed it is returned back to the developer (this is called as Reopen)

Risk-based Testing|Risk analysis techniques

2010-01-16T10:08:00.000-08:00

Testing is the means used in software development to reduce risks associated with a system. By testing, we hope to identify many of the problems before they get to the customer, thereby reducing the system’s risk. Unfortunately, testing alone can’t find all of the bugs and with the rapid pace of application development in the today’s world, testing has become a challenging proposition and often just doesn’t get done.

Trying to meet even tighter deadlines while still delivering products that meet customer requirements is the greatest challenge testers face today. Formulating answers to age-old questions like “What should we test?” and “How long do we test?” requires different strategies in fast-paced environments.

Does the product meet our quality expectations?
Is the application ready for users?
What can we expect when 2,000 people hit the site?
What are we risking if we release now?

Outcomes:

Risks and risk reduction techniques relative in software testing
Risk analysis techniques designed to identify software testing related risks
Test design strategy based upon risk analysis

Testing Cycle:A sample

2010-01-10T07:40:00.000-08:00

Although variations exist between organizations, there is a typical cycle for testing. The sample below is common among organizations employing the Waterfall development model.

Requirements analysis: Testing should begin in the requirements phase of the software development life cycle. During the design phase, testers work with developers in determining what aspects of a design are testable and with what parameters those tests work.
Test planning: Test strategy, test plan, testbed creation. Since many activities will be carried out during testing, a plan is needed.
Test development: Test procedures, test scenarios, test cases, test datasets, test scripts to use in testing software.
Test execution: Testers execute the software based on the plans and tests and report any errors found to the development team.
Test reporting: Once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release.
Test result analysis: Or Defect Analysis, is done by the development team usually along with the client, in order to decide what defects should be treated, fixed, rejected (i.e. found software working properly) or deferred to be dealt with later.
Defect Retesting: Once a defect has been dealt with by the development team, it is retested by the testing team. AKA Resolution testing.
Regression testing: It is common to have a small test program built of a subset of tests, for each integration of new, modified, or fixed software, in order to ensure that the latest delivery has not ruined anything, and that the software product as a whole is still working correctly.
Test Closure: Once the test meets the exit criteria, the activities such as capturing the key outputs, lessons learned, results, logs, documents related to the project are archived and used as a reference for future projects.

Testing Scope

2009-12-14T07:04:00.000-08:00

•

Whether you need ad hoc testing, automated, or just application profiling, our engagement implementation roadmap can address every need from your testing life cycle.
Test Planning: Test strategy, test objectives & approach.
Test Analysis & Design: Analyze functional requirements, make automation decisions, design test cases, design test environments.
Test Environment: Install HW, SW, test tools, and perform a smoke test.
Test Implementation: Develop test scripts and create test data.
Test Execution & Reporting: Execute test cases and test scripts, test report & metrics, and defect management.
Test Completion: project acceptance, delivery of test ware, postmortem.
Project Management: Tracking and control of testing processes, overall managed testing initiatives.
Configuration & Change Management: Version control, source control, change management, configuration items.

Testing process documentation

2009-12-10T22:22:00.000-08:00

The application of up-to-date techniques and approaches and the performing the right kind of test at the right time are key to the testing strategy. The QA department performs the following types of testing: functional testing, security and access control testing, installation testing, system testing, user interface testing, cross-browsers testing, integration testing, regression testing and performance testing.

Types of Testing Offered:

•Functional/regression testing
•API testing
•Performance/load/stress testing
•Compatibility/configuration testing
•Usability testing
•Security testing
•Data migration/conversion testing

Defects registration and tracking

2009-12-03T07:12:00.000-08:00

•We use dedicated systems to record the defects identified in software applications. They allow tracking the life cycle of a bug from the moment of its detection up to the moment of its elimination from the product. All the members of the team involved in the project development process have access to these systems with the appropriate rights assigned to them. The client is a key participant and can follow the testing process as it progresses and enjoys a full awareness of quality changes occurring in the developed application.

Strategic execution of testing

2009-12-02T05:32:00.000-08:00

•The application of up-to-date techniques and approaches and the performing the right kind of test at the right time are key to the testing strategy. We can successfully perform the following types of testing: functional testing, security and access control testing, installation testing, system testing, user interface testing, cross-browsers testing, integration testing, regression testing and performance testing.

Testing Services Focus

2009-11-27T06:21:00.000-08:00

Our Focus: We concentrate solely on testing software, business processes, and IT with the goal of helping our customers to achieve the benefits of their technology-enabled change faster. We are committed provide a full service to support all the ongoing software testing needs of an organization or business unit. It usually incorporates test management, functional testing and specialist test services as required. As individuals, we constantly adapt our approach for new situations, or to bring fresh insight to a familiar landscape. Although we are very experienced testing consultants, we are committed to continually improving our skills. We place a high value on training and coaching in advanced peer groups.

Our approach is:
 Reduce the cost of change
 Increase the speed of change
 Improve the governance of change

“Identifying and mandating good practice is not enough, You also need to tackle why programmes and projects fail in testing services, why test process improvement is inadequate on its own, and how you can overcome the pejorative view people often have of testing which itself can stifle progress.”

So ,Our testing service will enable you to maximize the value you derive from testing. As with our services are designed for test reduction: reducing the time spent testing, the cost of testing and the risks to going live.

Academic Details

2009-11-25T05:38:00.000-08:00

With A Vision : "To be a globally renowned, group of individuals who provides best of end-to-end testing solutions, leveraging technology, delivered by passionate, knowledge driven people". We have experience on various domains with Innovative concepts and with our unique value proposition of offering better, faster and less expensive testing, we think we are able to compel our clients to have a long-term relationship. We believe, we will be ethical, sincere, open, and direct in dealings with clients and each other. We promise, we will try to maximize business value for our clients by innovative ideas and experienced testing processes

In our group, we have people holding a bachelor's degree from universities
(Like PTU, UPTU and PU) in engineering, master degree in information sciences (from AIMA) and computer applications (From KUK).

Domain Experience detail

2009-11-23T23:35:00.000-08:00

Being in IT industry from last 5 years, we have worked for various domain projects. Now we wish to emerge our selves as a group of testing professionals(TQAS) , so will like to share our experience details.The main motive here is only to show the transparent picture of the kind of work we have been doing or done.

Project Experience detail:

Interactive Domian: Project is Java Conditional Access system. It is based on Interactive/Media Domain. As Client is changing their legacy system to new OCAP/True2way technology based STB’s. Customer can see EPG(Electronic programming guide, can order the VOD(Video on Demand, can order PPV(Pay per view) and can avail many more tru2way features. There is an in-build chip to do all the authentication from Headend side instead of separate smart card using in Legacy systems.

ETL Domain: Project is casual analysis tool which is used to review valuation request of a claim against total loss and hence reduce the claim settlement cycle time by electronically communicating. System also generates a wide range of report to be used by management and the client to study business trend for business analysis. System uses SSIS (SQL Server Integration Services) for BI (Business Intelligence) and SSRS (SQL Server Reporting Services) for reporting and UI solutions.

CRM Domain: This is a multi-phased project for upgrading Clarify CRM v6.1 to Amdocs CRM 6. This CRM tool facilitates Creation of Sales Orders, exchange requests, Return authorizations (RAs) for Service Department, sell accessories, manage hardware receipts into Service, and log test results and repair actions. The system provides the framework for creating a web portal into the CRM application.

Provisioning Domain: Project is an automated provisioning system for ISPs. Bundled services (e.g. Domain registration with e-mail and web hosting), otherwise known as packages, are created by the ISP in the Control Panel. Once a customer signs up for a package, the agents sequentially process the multitude of tasks (encapsulated in a Job) required, in order to provide the customer with access to use and manage their services. The software affords a lot of benefits like facilitating the effortless support of clients, enabling rapid resolution of problems, most transactions not requiring user inputs.

PLM Domain: The developed system is tool which is useful for product based companies to track and report the presence of Soc Substances of concern (Substances which can harm the environment) in their products or in the items they are using for the manufacture of their products and if the Soc Substances of concern are present then whether they are under threshold permissible limit or not.

Insurance Domain: Project is one of the most important Products in the property and casually insurance side, which provide all the functionality one might need for Insurance handling. System is divided in subsystem like UWS (Underwriting Workstations), CWS (Claims Workstation), BCWS (Billing & Collection Workstation). All of the subsystems are designed in such a way that they can be marketed stand-alone.

Travel Domain : Project has been designed as an online web based membership driven savings program. Individuals may log on to www.xyz.com, enroll as a member and then enjoy the savings benefits offered by its participating merchants. Benefits are grouped into the following general Categories:

1) Vacation benefits

2) Entertainment benefits

3) Home life benefits

These benefits are further divided into sub benefits. Member can take any of the benefit of his choice by taking the membership on the website. There is separate section for the members to access their accounts. After getting membership a Temporary membership card will issue to the member so that member can enjoy the benefits. On this card, members can take the discounts on each and every benefit.

Testing Experience Details

2009-11-23T07:24:00.000-08:00

TQAS group Have 5+ Yrs of experience on Quality Assurance and Testing domain. Proficient in Manual Testing and exposure in data ware house testing (ETL Testing ) reports testing using SQL query. In-depth experience in creating Test plan, Test strategy, Test cases, Test reports, Bug tracking and Traceability matrix.

Performed Product Based, Process Based, Database and Web Based Testing. Having domain knowledge Interactive (STB), Auto mobile Insurance , Billing and Customer management, Travel, Provisioning, Security Testing (Access Control System).

Good Exposure and knowledge of testing management tools--Quality Center, APTest Manager and Test Director.
Good Exposure and knowledge of bug tracking tools – Rational Clear Quest, JIRA , Bugzilla and Mantis
Good Knowledge with STB Testing, Functional Testing, Regression Testing, Integration Testing and etc.
Proficient in data ware house testing (ETL Testing ) reports testing using SQL query
Estimation, Test Planning & Test Management-Analyze of application requirements and design specifications.
Involved in developing Project Plan and Test plans for various Levels of testing.
Involved in various testing types like Audio/Video Testing, Firmware Testing, System Testing and Regression testing.
Done testing on the Production side.
Actively participation in enhancement meetings focused on making the application more effective.
Experience in gathering and managing test data.
Creating and Reviewing test scripts .
Generating test reports.
Maintaining Daily & weekly status reports and Time sheets.
Involved in User Manual preparation.
Good working knowledge on the Client/Server and Web Based Applications.
Fairly Good Experience in SDLC, STLC, Bug life Cycle.

Environment Exp: MS Windows Server 2003, MS .NET Framework 1.1, SQL Server 2005, MS Window 2000/XP, IE 6.0, Mozilla 5.0., SSIS , SSRS ,Linux/Solaris based,JSP, Perl, Python,Apache 2.0, Sun Web Server.

Testing & Quality Assurance Services

2009-11-22T05:50:00.000-08:00

TQAS is committed to providing high-quality solutions to its clients and as such we offer s structured QA process to assure that quality level. We take a serious approach to the testing process and quality assurance of the solutions that are developed either by our development team. We can also apply our vigorous QA to your existing or new applications that may not have been developed by our team. The goal of a QA process is either to prevent or uncover issues as early as possible in the process. Errors caught in design are much less expensive to remediate than errors found post-production in a live system. The current techniques and approaches applied to software testing help identify and prevent occurrences of problems associated with the weak functionality, low reliability, poor productivity, lack of scalability and other defects/bugs in the application(s). Our strong belief is to form a QA team in the initial stage of the project; this reduces the risks of fixing global bugs in later stages. The QA engineers are involved in the development process right off the mark: they are provided with the available documentation, acquainted with the business processes that are to be implemented in the project and technical specifications requested by the client. On the basis of the provided resources our engineers develop a testing plan that meets all the described requirements. It defines the scope of testing of the product and documents the process of the Quality Assurance Process.