WSO2 Quality Assurance

WSO2 Quality Assurance (QA) ensures product quality by using rigorous test cycles conducted on various technology stacks. At WSO2, we believe that having a methodical testing mechanism will add significant enhancements and value to our products.

You can contribute towards improving the WSO2 products by participating in the QA cycles of the WSO2 products. You will also be gaining exposure in software quality assurance at the same time.

To ensure that the software products meet the desired quality, it is imperative to have a dedicated QA team that employs proper testing mechanisms and methodologies.

If you are interested, simply Register with Oxygen Tank and take part in our QA process.

As a QA Contributor You Can:

1. Conduct functional tests on WSO2 products and report issues using JIRA
2. Propose test strategies
3. Create and update test scenarios and test cases
4. Create automation test scripts

When you actively participate in the QA process, you will get the opportunity to make decisions on product quality and releases and communicate with the development team on product issues via JIRA, issue tracker, developer mailing lists and forums.

WSO2 SQA Forum

Oxygen Tank offers Software Quality Assurance engineers an opportunity to discuss concepts, techniques and testing procedures used in professional Software Quality Assurance through our SQA Forum. All Oxygen Tank registered users can post topics to this forum. Note that WSO2 project specifc QA issues will not be discussed in this forum, instead will be disucussed in relevant project forums.

QA Artifacts

Different types of QA artifacts are produced during a QA cycle. They are live documents and the changes are reviewed by senior QA engineers at WSO2.

QA Test Cases and Checklists

A QA checklist is a summarized version of a test case. It does not describe the whole test scenario in detail. Instead, it assumes that the user has a better understanding of the product functional flows.

QA Executables

QA executables such as test suites and test frameworks for WSO2 projects can be found in WSO2 QA repository in the SVN.

QA Test Plan

A test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. A formal test plan will be maintained for each WSO2 project, which describes the following items in detail.

• Schedule
• Test environment
• Features to be tested
• Features not to be tested
• Test deliverables

WSO2 Carbon:	WiKi | SVN Repo
WSO2 ESB for Java :	WiKi | SVN Repo
WSO2 WSAS:	Wiki | SVN Repo
WSO2 Data Services :	Wiki | SVN Repo
WSO2 Identity Solution :	Wiki | SVN Repo
WSO2 Mashup Server :	Wiki | SVN Repo
WSO2 Registry :	Wiki | SVN Repo
WSO2 wsclient :	Wiki | SVN Repo
WSO2 WSF/AJAX :	Wiki | SVN Repo
WSO2 WSF/C :	Wiki | SVN Repo
WSO2 WSF/Java :	Wiki | SVN Repo
WSO2 WSF/Spring :	Wiki | SVN Repo
WSO2 WSF/JavaScript :	Wiki | SVN Repo
WSO2 WSF/PHP :	Wiki | SVN Repo
WSO2 WSF/Perl :	Wiki | SVN Repo
WSO2 WSF/Ruby :	Wiki | SVN Repo
WSO2 WSF/Python :	Wiki | SVN Repo
WSO2 WSF/C++ :	Wiki | SVN Repo
WSO2 Commons :	Wiki | SVN Repo
WSO2 User Manager :	Wiki | SVN Repo
WSO2 Mercury :	Wiki | SVN Repo
WSO2 Codegen :	Wiki | SVN Repo
WSO2 Tracer :	Wiki | SVN Repo
WSO2 Utils :	Wiki | SVN Repo
WSO2 Utils :	Wiki | SVN Repo
WSO2 Mex :	Wiki | SVN Repo
WSO2 Performance Benchmarks :	Wiki | SVN Repo
WSO2 Sadehsa2 :	Wiki | SVN Repo
WSO2 Statistics :	Wiki | SVN Repo
WSO2 Admin UI :	Wiki | SVN Repo
WSO2 Throttle :	Wiki | SVN Repo
WSO2 XFer :	Wiki | SVN Repo
General :	Wiki | SVN Repo