Android Application Development
Following process will be followed throughout the Project top to bottom approach:
- Testing
- Execute on
- Planning and Requirement
- Prepare manual testing case while
- understanding
- requirement understanding
- Coding
- Unit testing along with that developer testing
- Development done
- Usability Testing, Functionality testing
- Bug fixes
- Regression testing
- System ready
- Compatibility testing and system testing
- Performance, Stress and Load
- Application behaviour will be tested against
- Testing
- heavy loads
- Build testing
- Build testing on build environment
Planning and Requirement understanding
During requirement gathering phase test team will prepare manual test cases as per requirement. Complete Test plan along with test cases would be maintained in Testopia or any other test-case management tool based on your comforts, like 'Test Track' , 'X Studio' etc.
Coding
During development phase developers can perform Unit Testing to check against coding errors and do Developers testing to test the functionality from developers side. Nunit or MS Test will be used for the unit testing based on your suggestions. Both of the tools allow creation of test methods and are integrated with Visual Studio, which can also be customized to write specific test methods for the unit testing. Any error returned by such methods will stop successful compilation of code and will be needed to be resolved first. Which will make sure successful unit testing is done. Our preference would be to use MS Test as its provided by Microsoft and have more detailed integration with Visual Studio.
For the developers testing , developers would check against the check-list provided by test team. Which they will submit when the completed work is handed over to QA team. The same will be attached with the release package. Sample format of such check-list is attached with this package.
Development complete
Once developers are done with developer testing, that module will be given to test team for testing. Test team will start with adhoc testing by running manual test cases prepared in Test-case Management tool. Any bugs found, will be logged in Bugzilla or any other bug management tool. For major features, test team will prepare automated test scripts using Watir. Testopia does allow to maintain such script directly under tool itself.
Frequently Asked Questions
What is QA Process?
QA Process delivered by Balianti.
How does Balianti approach qa process?
We start with a 30-minute discovery call, scope a fixed-price proposal within 48 hours, prototype key flows, build in weekly sprints with Friday demos, launch with zero downtime, and offer an optional support retainer. Same process for every qa process engagement.
How long does a typical qa process project take?
Scoped work ships in 4-12 weeks depending on scale. Discovery and proposal are free and delivered in 48 hours. You will see working software every week.
What technologies does Balianti use for qa process?
Our core stack includes Node.js, React, Next.js, TypeScript, PostgreSQL, Python, .NET, Java, Flutter, React Native, AWS, Azure, and Google Cloud. We will recommend the right stack for your specific requirements.
How do I get a quote for qa process?
Call 475-221-9774, email [email protected], or submit the form on any page of this site. We reply within one business day with a scoped proposal and fixed pricing where possible.