- Open source
- Supports Windows and Ubuntu
- JavaFX to implement awesome interface
- Based on Rest-Assured, TestNG and Jxl
- Supports REST/SOAP webservices test automation
- Can handle correlated webservices
- Data-Driven tool
- Tasks parallel execution can be done by simple configuration
- Generates pie charts showing each project status and html reports showing each test cases status (Passed/Failed)
- Can be integrated with Jira to log bugs automatically as soon as any test case fails
- Generates logs on the execution runtime to monitor tool status continuously
-
Root: which contains all project files
-
Test Data: in which the automation tester can load all XLS files they need to be reused all over the project. For more details about writing test data, you have to check this link: https://github.com/ymhmd/API-Testing-Automation-Framework
-
Test Suite: project can be divided into test suites to be more organized. Test suite is the smallest project component to be executed and to be integrated with Jira. For each test suite, two parameters should be set, the first called
Threads
which helps the parallel execution in case number of threads is more than one, the second calledVerbose
which indicates how much details of test suite execution on logs section. In case Jira integration is enabled, you must set more parameters related to your Jira account and project. Lets have a look on them:
Domain
: Jira domainEmail
: Jira account emailPassword
: Jira account password. Email and password are required to authenticate to Jira accountIssue Type
: Bug/Task/SubtaskProject key
: in which project of Jira account to log bugsPriority
: Bug priority to be set
-
Task: Under each test suite, there are one or more tasks. Tasks are the main buenoAPI scripts since they refer to test data which can be executed. Each task has two parameters to be set, Excel file and the relevant Excel sheet.
-
Reports: As soon as execution is done, two types of reports are automatically generated. The first type is pie-chart showing the whole project status in terms of number of passed/failed test cases. The second type is more detailed reports which are customized version of html TestNG reports. Each task has its html report showing why each step in your test case is failed.
- NOTE: Logging bugs to Jira is done only in case at least on test case is failed. In other words, in case no test cases are failed, no bugs would be logged into Jira even thought Jira integration is enabled. If you disable Jira integration, no bugs are logged into Jira even if some test cases are failed.
-
Click on buenoAPI executable file
-
In welcome screen, you can Create new project or import project which you created before
-
Create new project by selecting directory to save the project.
-
Project is created. buenoAPI project screen is displayed with the main 5 components discussed before.
-
Test Data and Reports components are empty since no XLS files are loaded nor test suites are executed.
-
Load test data:
- Create Test Suite:
- Add suite parameters without Jira integration:
- Add suite parameters without Jira integration:
- Set
Verbose
to 3 - Set
Threads
to 1 - Enable
Jira
check box - Set Jira
Jira Domian
- Set your
Jira Email
- Set your
Jira Password
- Set
Project Key
- Set
Issue Type
- Set
Priority
- Save Test Suite
- Right click on created test suite
- Click on Save in the menu
- Add Task under Test Suite
- Add Task parameters
- Set
Excel File
to one of XLS files imported in the project - Set
Excel Sheet
to sheet name in the selected XLS file - Right click on Task > Save
- Execution
- Navigate to Test Suite you want to be executed
- Click on Start Green Arrow button
- Test suite execution is logged in Logs section at the bottom of the screen
- Wait till the execution is Done
- Reports