• Games Testing Solutions

    We offer Game QA Testing services on most platforms which include iPhone, iPad, Android based Tablets/Mobile devices, PC, MAC etc

  • Automation Testing

    Automation testing is primarily used for performing regression testing of a product. Regression testing requires execution of Test Cases with every build.

  • Affordable Testing Solutions

    Precise Testing Solution are fully committed to deliver organize, systematic and best-in-class quality assurance, adopting latest authentic mythologies of industry..

Thursday, 31 July 2014

Posted by Sandeep kr | 00:27 | No comments

Bottom up Testing

This testing technique comes under integration testing. In this testing approach programmer can interconnect sub programs without involving a main program due to main program is under construction. In the place of the under constructed main program the programmer can use a temporary code is called Driver. So, that lower level of components is to test first. In this testing the testing flow is from bottom to top.

The process repeated unless the components at the top level of the hierarchy are to be tested. Bottom up is more advantageous became it is easy to create driver rather creating a stub and can serve multiple purposes.

Example: If A, B & C are three Module, if Main module A is under construction. In this testing, the Developer can take the help of a Temporary program that called as Driver to check the communication between the modules.

Wednesday, 30 July 2014

Posted by Sandeep kr | 00:11 | No comments

Black Box Testing

Black box testing is the method for Software testing and used to test the functionality of any application. This can apply on any level of testing. In this testing test any application without knowing the internal structure of the software. In Black box testing the tester knows what the inputs is and what should be the result of that input.


The main purpose of the Black Box is to determine the software is working as per the user expectation in requirement document & whether it is meeting the user expectations or not. In these testing testers can find the errors like Incorrect or missing functions, Interface errors, Mistakes in data structures and external database accession, Behavior or performance errors, Initialization & termination errors. The Black box testing technique we can see BVA (Boundary value analysis), ECP (Equivalence class partitioning), DT (Decision table), STF (State transition flow) a d EG (Error Guessing). In this testing tests are done from the user point view & will help exposing the specifications. For this testing tester not need know about the programming languages or not to know how the software has been implemented. This testing method mostly use testers in there practical life.

Example: - a tester doesn’t have knowledge about the internal architecture of the application but can test application using browser by providing inputs through keyboard and mouse.

Thursday, 24 July 2014

Posted by Sandeep kr | 23:52 | 1 comment

Binary Portability Testing

This testing is used test the portability of the software by executing the software on different platforms and environment. It is used for conformation of an Application Binary Interface (ABI) specification. The conformation to an Application Binary Interface (ABI) specification. The Binary Portability testing  should be carried on different types of software program platforms, such as Windows(x86, X86-64), Linux, Mac OS, Java, Solaris, and Android. If application is highly portable then user can run application in any platform and will increase the demand of the product or project. If you build any software then for portability testing we need to execute the software on different operating system or if it’s a web software then we need to run on different browsers to check the portability of build software. Software should be portable so that the user can operate on any platform.

Wednesday, 23 July 2014

Posted by Sandeep kr | 23:13 | 1 comment

Baseline


It is one of the type of non-functional testing.  It is used for validation of documents and specifications on which test cases will be design. The SRS validation is baseline testing. It is used to define the base for any construction or for measurement, comparisons or calculations. This testing is also doing help for solving most of the problems that are discovered. A majority of the issues are solved through baseline testing. This testing helps to clear the requirement of the user and help to understand the overall need of the customer. If the requirements document is completely verified then it will help to build the quality software. It defines the work activities related to the software development process.

Tuesday, 15 July 2014

Posted by Precise Testing Solution | 02:17 | 1 comment
Security testing is type of testing, where we test the application and try to find all loop holes and try to prevent form unauthorized access of application.
Now security testing is not only  necessity for website and web application. Now hacker are try to hack you mobile, your online data, your digital locker. Now security is one of manor challenge of all software to prevent unauthorized access.
We know, you cannot trust any application and you do not want to register in any website where security is not good.
These are some security testing type; we can test security of application according to nature of application.

No.
Type of security testing
1.1
Information Gathering
1.2.
Conduct Search Engine Discovery and Reconnaissance for Information Leakage
1.3
Fingerprint Web Server
1.4
Review Webserver Metafiles for Information Leakage
1.5
Enumerate Applications on Webserver
1.6
Review Webpage Comments and Metadata for Information Leakage
1.7
Identify application entry points
1.8
Map execution paths through application
1.9
Fingerprint Web Application Framework
1.10
Fingerprint Web Application
1.11
Map Network and Application Architecture
2.1
Configuration and Deploy Management Testing
2.2
Test Network/Infrastructure Configuration
2.3.
Test Application Platform Configuration
2.4.
Test File Extensions Handling for Sensitive Information
2.5.
Backup and Unreferenced Files for Sensitive Information
2.6.
Enumerate Infrastructure and Application Admin Interfaces
2.7.
Test HTTP Methods
2.8.
Test HTTP Strict Transport Security
2.9
Test RIA cross domain policy
3.
Identity Management Testing
3.1
Test Role Definitions
3.2
Test User Registration Process
3.4
Test Account Provisioning Process
3.5
Testing for Account Enumeration and Guessable User Account
3.6
Testing for Weak or unenforced username policy
3.7
Test Permissions of Guest/Training Accounts
3.8
Test Account Suspension/Resumption Process
4.
Authentication Testing
4.1
Testing for Credentials Transported over an Encrypted Channel
4.2
Testing for default credentials
4.3
Testing for Weak lock out mechanism
4.4
Testing for bypassing authentication schema
4.5
Test remember password functionality
4.6
Testing for Browser cache weakness
4.7
Testing for Weak password policy
4.8
Testing for Weak security question/answer
4.9
Testing for weak password change or reset functionalities
4.10
Testing for Weaker authentication in alternative channel
5
Authorization Testing
5.1
Testing Directory traversal/file include
5.2
Testing for bypassing authorization schema
5.3
Testing for Privilege Escalation
5.4
Testing for Insecure Direct Object References
6
Session Management Testing
6.1
Testing for Bypassing Session Management Schema
6.2
Testing for Cookies attributes
6.3
Testing for Session Fixation
6.4
Testing for Exposed Session Variables
6.5
Testing for Cross Site Request Forgery
6.6
Testing for logout functionality
6.7
Test Session Timeout
6.8
Testing for Session puzzling
7
Data Validation Testing
7.1
Testing for Reflected Cross Site Scripting
7.2
Testing for Stored Cross Site Scripting
7.3
Testing for HTTP Verb Tampering
7.4
Testing for HTTP Parameter pollution
7.5
Testing for SQL Injection
7.6
Oracle Testing
7.8
MySQL Testing
7.9
SQL Server Testing
7.10
Testing PostgreSQL
7.11
MS Access Testing
7.12
Testing for NoSQL injection
7.13
Testing for LDAP Injection
7.14
Testing for ORM Injection
7.15
Testing for XML Injection
7.16
Testing for SSI Injection
7.17
Testing for XPath Injection
7.18
IMAP/SMTP Injection
7.19
Testing for Code Injection
7.20
Testing for Local File Inclusion
7.21
Testing for Remote File Inclusion
7.22
Testing for Command Injection
7.23
Testing for Buffer overflow
7.24
Testing for Heap overflow
7.25
Testing for Stack overflow
7.26
Testing for Format string
7.27
Testing for incubated vulnerabilities
7.28
Testing for HTTP Splitting/Smuggling
8
Error Handling
8.1
Analysis of Error Codes
8.2
Analysis of Stack Traces
9
Cryptography
9.1
Testing for Weak SSL/TSL Ciphers, Insufficient Transport Layer Protection
9.2
Testing for Padding Oracle
9.3
Testing for Sensitive information sent via unencrypted channels
10
Logging
10.1
Test time synchronization
10.2
Test user-viewable log of authentication events
11
Business Logic Testing
11.1
Test Business Logic Data Validation
11.2
Test Ability to Forge Requests
11.3
Test Integrity Checks
11.4
Test for Process Timing
11.5
Test Number of Times a Function Can be Used Limits
11.6
Testing for the Circumvention of Work Flows
11.7
Test Defenses Against Application Mis-use
11.8
Test Upload of Unexpected File Types
11.9
Test Upload of Malicious Files
12
Client Side Testing
12.1
Testing for DOM based Cross Site Scripting
12.2
Testing for JavaScript Execution
12.3
Testing for HTML Injection
12.4
Testing for Client Side URL Redirect
12.5
Testing for CSS Injection
12.6
Testing for Client Side Resource Manipulation
12.7
Test Cross Origin Resource Sharing
12.8
Testing for Cross Site Flashing
12.9
Testing for Clickjacking
12.10
Testing WebSockets
12.11
Test Web Messaging
12.12
Test Local Storage


Monday, 14 July 2014

Posted by Sandeep kr | 04:24 | 1 comment

Software Testings

Conformance Testing

Conformance testing or type testing is use to determine whether our software meeting the specific standard or not. These standards are defined and used by accosts world like  autonomous entities such as the Institute of Electrical & Electronics Engineers (IEEE), or the World Wide Web Consortium (W3C) and the European Telecommunications Standards Institute (ETSI).


Data Driven Testing

This testing is use to perform the testing for multiple data values. The test input and output values can directly access from the table. In a data-driven testing, a set of user’s activity is run with multiple input values. Data impulsive allows one script to the test of application functionality with many sets of data. This direction, testers can test how the application handles many inputs effectively.

Dependency Testing

Examines the application requirement for preexistence software, initial states & configuration in order to hold the proper functionality. The impacted areas of the application are also tested when testing the new features or existing features.

Saturday, 12 July 2014

Posted by Sandeep kr | 01:58 | 1 comment

Component Testing

Component testing is that in which we test those test objects which are separately testable and without integrating with other components. Component testing is done by the tester and always before component testing unit testing is conducted by the developer. Component testing is consider as module testing, because we are testing each module differently and effectively.

Compatibility testing is a type of non-functional testing. In this testing we test that our software is compatible with the computing environment. Such as operating system, Hardware  platform, database, browser compatibility, other system software.

Concurrency Testing

If the multiple users are using our software concurrently then how the system are performing. Concurrency is nothing but having multiple users performs same actions at same time. It helps in identifying and measuring the problems in response time, levels of locking and deadlocking in the application. Load runner is widely use for this testing which will help to create the virtual environment and will look like that multiple users are using the same application at same time. Concurrency testing is also called multi-user testing.

Bookmark Us

Delicious Digg Facebook Favorites More Stumbleupon Twitter