Looking for the needle in the hay stack? Applications and users can report a huge amount of software errors. Sorting them and prioritizing them can be a daunting task - tedious and highly time-consuming. The last thing you want is your development team spending copious amounts of time analysing bugs in code when this time can be better spent doing what they do best. We are here to help with trained Quality Engineers trained with Agile development methods who debug beyond the basic user interface. Our team will gather bugs, evaluate them and assign them to the right developers. We utilise the Scrum approach to provide cross-functional interaction with development teams and are able to communicate with your developers at the code level. We are here to ensure bugs are fixed on-time, every time!

Coding and Developing

We are a real company with no stock photos. See some of our staff at work, talking on the Internet with our customers while helping them develop their application.

More about Quality Assurance

Quality Assurance (QA) refers to planned and systematic production processes that provide confidence in a product's suitability for its intended purpose. It is a set of activities intended to ensure that products satisfy customer requirements in a systematic, reliable fashion. Two key principles characterize QA: "fit for purpose" (the product should be suitable for the intended purpose) and "right first time" (mistakes should be eliminated).

To accomplish the process of real QA work we follow a number of procedures and make use of effective tools outlined below.

What We do:

• Black box testing - treats the software as a "black box," without any knowledge of internal implementation. Black box testing methods include: equivalence partitioning,boundary value analysis,all-pairs testing, fuzz testing, model-based testing,traceability matrix, exploratory testing and specification-based testing.
• White box testing - by contrast to black box testing, is when the tester has access to the internal data structures and algorithms (and the code that implements these). White box testing methods include: API testing, code coverage, fault injection, mutation testing, static testing.
• Grey box testing - involves having access to internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level.
• Acceptance testing - A smoke test is used as an acceptance test prior to introducing a build to the main testing process, User Acceptance Testing.
• Regression testing - is any type of software testing that seeks to uncover software regressions. Such regressions occur whenever software functionality that was previously working correctly stops working as intended.
• Non Functional Software Testing - Special methods exist to test non-functional aspects of software. Performance testing, Usability Testing, Security Testing. Non-functional testing verifies that the software functions properly even when it receives invalid or unexpected inputs.

Tools Used

Test Case Management Tools

Test Run - Collaborative test planning that's just simple enough.

• Create, manage and execute test plans
• Track efficiency and progress with graphical reports
• Works with Spreadsheets and bus trackers you already use.

Project Management Tools

JIRA - lets you prioritise, assign, track, report and audit your issues, whatever they may be - from software bugs and help desk tickets to project tasks and change requests. It is an extensible platform that you can customise to match to your business processes.


FOGBUGZ - helps teams work together by tracking, prioritizing, and coordinating the thousands of small tasks development team has to do.Its web based so everyone on the team always sees the whole picture. Feature requests, customer email,bugs, even high level design discussions are instantly searchable and trackable.


SCRUMY - is a simple and intuitive virtual task board based on some concepts of Scrum that helps organize and manage your projects.


FISHEYE - gives your source code repository (Subversion, CVS or Perforce) a simple Web interface. Developers can use FishEye to browse directly to a file or directory, traverse deep directory hierarchies quickly, and see visualizations of a branch history for an individual file.

Others

We also can use Spreadsheets for writing test cases and documenting all issues depending on what is convenient for you.

Automation Scripts can also be written and run by us.

Whatever Method suits you and your budget we are ready to work with that for you.

---