LinX Technology Inc.

LinX Technology Inc. offers an immeasurable testing knowledge base.  With over 50 years of combined testing experience we can provide clients with a solid framework/methodology that can be utilized throughout the organization.

We firmly believe that testing is the process of executing a process with the intent of finding errors. In addition code, processes (support model) and documentation (installation guide) must be tested.  

 Testing Is....

• The pursuit of excellence
• Continuous improvement
• Doing the right things, right
• Not doing wrong things
• Not high costing
• Exceeding customer’s expectations

The vision and goal of testing is to deliver a product that the user will recognize as stable and viable that meets the original overall vision.

Why Test?

• Quality ---Quality---Quality
• Trends in technology
• Transition to client/server
• Transition to internet
• Interaction with external entities
• Reduce system downtime
• Reduce support call cost
• E-Business

There are several types of testing initiatives in which LinX Technologies Inc. is highly experienced in leading; and they are:

• Unit Testing  - The purpose of unit testing is for a developer and/or tester to verify that the software works according to design specifications.
• Integration Testing – The process of testing the functionality and interaction between two or more applications.
• Regression Testing – These tests are used for comprehensive re-testing of software to validate that all functionality and features of previous builds (or releases) have maintained integrity of features and functions tested previously.  This suite of tests includes the Full Functionality tests and bug Regressions Tests (automated and manual).

• Acceptance Testing – Formal tests conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept a system.

• Performance Testing – These tests are the measurement and prediction of performance (e.g. Response time and/or throughput) for a given benchmark workload.

• Parallel Testing – Testing by processing the same (or at least closely comparable) test workload against both the existing and new versions of a product, then comparing results.
• Stress Testing  -  These tests check for factors such as Cross – Tool testing,  memory management and other operating system factors.
• Functionality Testing – This test is designed to test the full functionality, features, and user interfaces of software based upon the functional specifications.

Leveraging our prior work and knowledge of testing framework/methodology with key experienced resources from our team, we will bring a combination of dedication and “know how” to ensure project success.