Quality Assurance Processes

Software quality assurance (SQA) is all about monitoring the used software engineering processes and to ensure quality of the end product.

Rapidsoft's Software Quality Assurance services encompass the entire software development process. Following are processes followed for Quality Assurance of mobile and web applications:

Usability Testing

• Preparing list of functionalities
• Verifying Look & Feel (User Interface testing)
• Verifying navigation from end user comfort perspective (for each functionality)

Functional Testing

• Creating test cases
• Executing test cases to ensure that all features/functionalities work as expected.
• Testing execution would be on Simulators and Real Devices.
• Retesting defect fixes once defects reported by tester are fixed by developers.

Regression Testing

• Identification of Regression Test scenarios.
• Creation of Regression Test suite.
• Execution of Regression Test Suite.

Network (Need to consider for live environment)

• Ensuring network disconnects and low signal strength does not adversely affect the app's functionality.
• The user's permission to use the network connection or other billable event is requested.
• Network exceptions are handled and the user is notified about them.
• The network connection is closed when it is not needed anymore and/or when the application is closing.
• Check for WIFI, Internet connectivity
• Check for data connection

Aesthetics Rating

• An independent assessment that includes comments on the layout, color schemes, fonts, graphics etc
• Performance and Reliability
• The application does not affect the use of the system features or other applications.
• There are no bottlenecks in the code.
• Communication to and from the device/application is kept within reasonable limits.

Memory Utilization

• The application does not consume device's running power and memory excessively.
• Only necessary data is saved into the flash memory.
• Occasional tasks, exceptional tasks (like those for emergency conditions), and tasks that cope up with errors (like those caused by interruption of network connection during application's use) must be considered and treated appropriately.

Application Security

• Sensitive data is encrypted before it is stored into the device.
• Role based access verification (Authentication)
• Session Management

Environmental Changes (Need to consider for live environment)

• The application works correctly even though the environment may change.
• The application runs even though exceptions are handled at the same time.
• The user is informed in extraordinary situations.

Reporting

• Testing related bugs would be reported using Mantis as bug reporting and management tool.

Testing Matrix

Types of Testing	Manual Testing		Platforms
	Using Simulators	Using Devices	iPhone/iPad Android/Windows Mobile/BlackBerry	Windows PC
Functional Testing
Usability Testing
Negative Test
User Interface Test
Network Test
Aesthetics Rating
Compatibility Testing
Memory Utilization
Application Security
Synchronization testing
Performance and Reliability

Platform specific Testing

Web

• Testing would be done on Linux/Windows platform on 32-bit OS (during development and construction stages).
• UI testing would be done based on User Interface Guidelines for RoR based platforms.
• Input modes
• QWERTY Keyboard
• Initial testing will be done for the target OS enlisted below. Other OS will be tested for separate porting development tasks.
• A due assistance and support for same can be provided during User acceptance tests.

Android

• Testing would be done on Simulators (during development and construction stages) and Real devices.
• UI testing would be done based on User Interface Guidelines of Android.
• Input modes
  • Single touch
  • Multiple touch
  • Virtual Keypad
• Initial testing will be done for the target handset enlisted below. Other handsets will be tested for separate porting development tasks.

iPhone/iPad

• Testing would be done on Simulators (during development and construction stages) and Real devices.
• UI testing would be done based on User Interface Guidelines of iPhone.
• Input modes
  • Single touch
  • Multiple touch
  • Virtual Keypad
• Initial testing will be done for the target handset enlisted below. Other handsets will be tested for separate porting development tasks.
• iOS 4.x – iPhone.
• A due assistance and support for same can be provided during User acceptance tests.

Windows Phone

• Testing would be done on Simulators (during development and construction stages) and Real devices.
• UI testing would be done based on User Interface Guidelines of WP 07.
• Input modes
  • Single touch
  • Multiple touch
  • Virtual Keypad
• Initial testing will be done for the target handset enlisted below. Other handsets will be tested for separate porting development tasks.
• WP 07 – HTC HD 7
• A due assistance and support for same can be provided during User acceptance tests.

BlackBerry

• Testing would be done on Simulators (during development and construction stages) and Real devices.
• UI testing would be done based on User Interface Guidelines of BB.
• Input modes
  • Single touch
  • Multiple touch
  • Virtual Keypad
• Initial testing will be done for the target handset enlisted below. Other handsets will be tested for separate porting development tasks.
• BB 10 – BlackBerry 10 Z
• A due assistance and support for same can be provided during User acceptance tests.