Origin Market is a fin-tech startup, which has built first one of the prime network connecting borrowers and dealers in the fixed income primary markets, simplifying the process for bond issuance globally.

Summary of the Product

With respect to its application, origin market helps its dealers automate many of the manual tasks involved in bond origination. It works by maximizing the relationships between issuers and investors over a suite of scalable information asymmetries to sell-side banks for smoother business performance. This greatly increases the opportunities and velocity in larger and less liquid corporate bond trades between banks, institutional investors and exchanges. Origin Market introduced newer products to build the first network online platform for issuers of private placements to post desired sizes, terms and maturities for new offerings directly to the 50 biggest global investors. It created a new trade route to cut middle regular providers of such funding without going through the bank arrangers as usual. Origin clients are in 45 cities across 6 continents, and include some of the biggest names in fixed income.


Origin is hosted on the cloud, built with the latest technology and is accessible on the web
(nothing to download)
Backend: Python, Django, Java
Frontend: Angular JS, Angular, Knockout


3+ year


Being a startup Origin Markets had no Testing process in place and also they did not maintain any documentation with respect to product features. Thought frameworks brought in there QA Expertise to implement a stringent testing process in order to deliver a high quality fin-tech product.

Technical challenges

1. Agile process is followed as requirement changes are available every week.
2. Testing has to be done for Multiple Accounts for each scenario on Multiple Browsers.
3. Testing was also done by downgrading the Firefox Browser.
4. Test Team is not involved in new feature discussions
5. Testing team is not given DB/Production access
6. Testing team created all the data required for the feature testing
7. Test Coverage focus towards:

  • Functional Testing
  • System Integration Testing
  • Adhoc/Exploratory Testing
  • Compatibility Testing

Test Phase

  • Requirement Analysis
  • Test Planning
  • Designing Test cases
  • Review Test Cases
  • Test Case Execution
  • Hotfix Testing
  • Defect Reporting
  • Defect Retesting
  • Regression Testing
  • Test Cycle Closure

Progress and Coverage
  • Release notes Testing
  • Bug Validation
  • Hotfixes Validation
  • All the Old & new features test case execution and reporting
  • All the Test cases Designing & Execution done using Zephyr(add on in JIRA)
  • All the Defects raised and assigned to dev admin using the bug tracking tool JIRA
  • Weekly QA status report summarizing the test execution summary, List of bugs raised trends and their status.
  • Testing is performed using Chrome,Firefox,Ie11,Edge in QA test Environment
  • Total Test Cases Designed – 476
  • Total Bugs Raised – 1681

Defect Reporting

  • Log Defects into JIRA.
  • Blocker bugs were immediately reported to the Developer team via SKYPE
  • Defect assigned to the Dev Admin for fixing.
  • Retest Hotfix provided for Blocker Bugs.
  • Reopen a Fixed Bug if it re-exists

Project Challenges Faced

1. For any new feature implementation, there is no demo or mock up provided to the
testing team, only a release note is provided with a short note of the new feature.
Testing team had to explore the new feature, understand, derive test cases and then
test the new feature.
2. Requirement changes on a regular basis resulting in constantly updating of the
existing Test cases.
3. Less time for Adhoc or even exploratory testing.
4. Few a Times if new Deployment fails then QA has to wait till its deployed resulting in
less execution time.
5. Complete UI was revamped as per client requirements, resulting in retesting of all
the modules & redesigning all the related test cases.
6. Few modules requirements are completely customized for some clients. So testing
has to be planned separately for those requirements.
7. Testing has to perform on 4 browsers using Chrome, Firefox, Ie11, and Edge for
different User team types.
8. Last Moment Hotfixes before Production Push needs to be thoroughly tested to avoid
slippages into Production environment.


  • End-to-end traceability from functional test scenario to test cases.
  • No Bug Slippage to Production Environment.
  • Implemented Direct Issuance platform that connect Issuers and Dealers from around the world and is used by 87 institutions across 17 dealers and 70 borrowers.
  • Identification of major defects and constantly modified test cases as per requirement change.


1. Sole ownership of modules assigned for testing.
2. Reported many issues which were not identified earlier
3. Took part in Sprint calls and ensured task completed was reported on time
4. Tested 125 + builds till today