Category: Usecases

Summary: In a project regression, you want to automatically create a jira on the suite/regression failure and the same jira will be marked to done/bug fixed state once the regression passes in future execution. This can be achieved by gempyp by using following tags: Tag NameTypeField TypeDescription String, Single valueOptionalSubscribed user can integrate GemPYP with JIRA. This would create a JIRA ticket in the test suite fails. String, Single valueMandatory if jira_email is passedJira Access Token to authenticate JIRA user. Integer, Single valueMandatory if jira_email is passedProject ID on of project on JIRA under which ticket will be created String, Single valueOptionalTitle for Jira Creation. Default will be the name of suite String, comma separatedOptionalJira transition from one stage to another. <data> <suite> <!--Here brigeToken and User are the jewel credentials--> <project-name>TEST_PY</project-name> <report-name>Pyprest Scenarios</report-name> <environment>prod</environment>…

  Background Suppose a monolithic architecture services needs to migrated to microservices architecture. There are numerous apis for that and many apis data are inter-dependent. Data between the services/apis are exchanged. Requirements So to ensure that the microservices apis has data and keys same as of monolithic one and code is capable to intelligent, then there comes numerous scenarios and testcases corresponding to the scenarios. Challenges It becomes difficult to manually check all the scenarios or automate from scratch using python or java scripts. Why Gempyp Even if you use Python/Java Frameworks to automate the scenarios, you won't be able to achieve the level of ease of automation, the time saved while automation, performance metrics of the apis, intelligent inter-dependency handling between testcases, data passing between testcases and many more.…

Overview of important tags: 1. source_db and target_db tags Mandatory for Database Comparison. Accepts a single string or dictionary. Values for single string can be “MySQL, PostgreSQL, Snowflake, custom” Dictionary is used for mongoDB where keys are “type, database and collection” where value of type is mongoDB. <source_db>Define type of database or custom</source_db> <target_db>Define type of database or custom</target_db> Example: <source_db>MySQL</source_db> <target_db>Custom</target_db> 2. source_conn and target_conn tags Mandatory for Database Comparison. Accepts a single string or dictionary. We provide database credentials or database connection string. Connection String corresponding to databases For Snowflake - snowflake.connector.connect(user="xxxxxxxxxx",password="xxxxxxxxxx",account="xxxx.ap-south-1",warehouse='COMPUTE_WH',database="SNOWFLAKE_SAMPLE_DATA",schema="TPCH_SF100") For MongoDB - pymongo.MongoClient(host=['mongodb+srv://xxxxxxxx:[email protected]/test'], connect=True) For MySQL - mysql.connector.connect(host='xxxxxxxxx',user='xxxxxxx', password='xxxxxxxxx',database='xxxxxxxxxxx',port=3306) For Postgresql pg8000.connect(host='xxxxxxxxx',user='xxxxxxx', password='xxxxxxxxx',database='xxxxxxxxxxx',port=3306) Scenario 1: Comparison between two tables in similar database <data> <suite> <!--Here brigeToken and User are the jewel credentials--> <project-name>TEST_PY</project-name> <report-name>Data Validation…

Automation testing can be done by creating test suites. Gempyp can be used to automate all types of tests for different technologies i.e., unit tests, functional tests, regression tests, smoke tests for technologies like API, UI, Data Comparison and Applications. These test suites can be scheduled to monitor the application functionality, can be integrated into CI/CD to deliver quality released. Continuous Testing using Gempyp CT is the practice of automating and integrating tests into the software delivery chain and automatically executing those tests against each build of the codebase. Jenkins, Gitlab, Github Actions are the few CI/CD applications. Test suites can reside in your development repository and you can integrate these test suites to run in the build pipeline. If the pipeline fails due to the test suites, then those…