| # |
Test Scenario |
Expected result |
Actual Test Result (pass/fail) |
Comments |
Test Result - 1.0RC1 (FF3/jdk15/winxp) |
Test Result - 1.0RC3 |
Test Result - 1.0RC4 |
| 1 |
Log in to Data service solution admin page
(user=admin/password=admin) |
User should be able to log in to admin page successfully |
pass |
|
pass |
Pass |
pass |
| 2 |
Enter invalid credentials |
An appropriate error message should be displayed and allow user to re-enter credentials |
pass |
|
pass |
Pass |
pass |
| 3 |
Select to create a new data service |
Step 1 of the data service wizard should be displayed |
pass |
|
pass |
Pass |
pass |
4 |
Save data service without copying the relevant jdbc driver in to classpath |
The data service should be deployed as faulty |
fail |
https://wso2.org/jira/browse/DS-324 |
pass |
Pass |
pass |
| |
|
|
|
|
|
|
|
| |
Data service wizard - Step 1 |
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| 1 |
Click on 'Next' without filling any value in the first step of data service configuration wizard |
'Name of the data service must be provided in order to proceed' message will be displayed |
pass |
|
pass |
Pass |
pass |
| 2 |
Select 'RDBMS' as the datasource and click add button |
'Data source type: RDMBS' window will be displayed |
pass |
|
pass |
Pass |
pass |
| 3 |
Select 'MS Excel' as the data source |
'Data source type: Excel' pop-up window will be displayed |
pass |
|
pass |
|
pass |
| 4 |
Select 'CSV' as the data source |
'Data source type: CSV' pop-up window will be displayed |
pass |
|
pass |
|
pass |
| 5 |
Select 'JNDIDatasource' as the data source |
'Data source type: JNDIDataSource' pop-up window will be displayed |
pass |
|
pass |
|
pass |
| |
|
|
|
|
|
|
|
| 6 |
Select 'MySQL' as the database type |
Default driver should be com.mysql.jdbc.Driver |
pass |
|
pass |
Pass |
pass |
| 7 |
Select 'Apache Derby' as the database type |
Default driver should be org.apache.derby.jdbc.EmbeddedDriver |
pass |
|
pass |
|
pass |
8 |
Select 'Microsoft SQL Server' as the database type |
Default driver should be com.microsoft.jdbc.sqlserver.SQLServerDriver |
pass |
|
pass |
|
pass |
9 |
Select 'Oracle' as the database type |
Default driver should be oracle.jdbc.driver.OracleDriver |
pass |
|
pass |
|
pass |
10 |
Select 'DB2' as the database type |
Default driver should be com.ibm.db2.jcc.DB2Driver |
pass |
|
pass |
|
pass |
| 11 |
Select 'HSQLDB' as the database type |
Default driver should be org.hsqldb.jdbcDriver |
pass |
|
pass |
|
pass |
| 12 |
Select 'Informix' as the database type |
Default driver should be COM.ibm.db2.jdbc.app.DB2Driver |
pass |
|
pass |
|
pass |
| 13 |
Select 'Generic' as the database type |
Default values should be populated as 'Generic' |
pass |
|
pass |
|
pass |
| |
|
|
|
|
|
|
|
14 |
Enter the jdbc url of a valid MySQL db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
pass |
|
pass |
Pass |
pass |
15 |
Enter the jdbc url of a valid Derby db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
pass |
|
not tested |
Pass |
not tested |
16 |
Enter the jdbc url of a valid MS SQL server db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
pass |
|
not tested |
|
not tested |
17 |
Enter the jdbc url of a valid Oracle db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
Not tested |
|
not tested |
|
not tested |
18 |
Enter the jdbc url of a valid Oracle db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
Not tested |
|
not tested |
|
not tested |
19 |
Enter the jdbc url of a valid DB2 db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
Not tested |
|
not tested |
|
not tested |
20 |
Enter the jdbc url of a valid HSQLDB db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
Not tested |
|
not tested |
|
not tested |
21 |
Enter the jdbc url of a valid Informix db, enter user credentials and click on 'Test Connection' |
'Connection successful' message will be displayed |
Not tested |
|
not tested |
|
not tested |
22 |
Click on 'Test Connection' with invalid DB URL |
Appropriate error message should be displayed |
pass |
|
pass |
Pass |
pass |
23 |
Click on 'Test Connection' with invalid JDBC driver |
Appropriate error message should be displayed |
pass |
|
pass |
Pass |
pass |
24 |
Click on 'Test Connection' with invalid username |
Appropriate error message should be displayed |
pass |
|
pass |
Pass |
pass |
25 |
Click on 'Test Connection' with invalid password |
Appropriate error message should be displayed |
pass |
|
pass |
Pass |
pass |
| 26 |
Shutdown DB and click on 'Test Connection' |
Appropriate error message should be displayed |
pass |
|
pass |
Pass |
pass |
|
|
|
|
|
|
|
|
| 27 |
Select MS Excel as the datasource and enter a valid excel datafile location in server file system |
dataservice configuration preview should be updated with the excel file path |
pass |
|
pass |
|
pass |
| 28 |
Select MS Excel as the datasource and enter a valid url based repository as the excel file location |
dataservice configuration preview should be updated with the excel file path |
fail |
|
pass |
|
pass |
|
|
|
|
|
|
|
|
| 29 |
Select CSV as the datasource and provide valid values for configuration parameters |
dataservice configuration preview should be updated with the given properties |
pass |
|
|
|
pass |
30 |
Enter a CSV file resides in server file system as the CSV path |
|
pass |
|
pass |
|
pass |
31 |
Enter a CSV file resides in a URL repo as the CSV path |
|
|
|
pass |
|
pass |
32 |
Verify mandatory attributes of Data Source Type:CSV popup window |
Starting Row, Header available fields should be mandatory |
pass |
|
pass |
|
pass |
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| |
Data service wizard - Step 2 |
|
|
|
|
|
|
| 1 |
Check the preview of the data service configuration |
The preview should be displayed correctly with the information provided in the first step |
pass |
|
pass |
Pass |
pass |
| 2 |
Select to create a new query |
'Add New Query' popup window should be displayed |
pass |
|
pass |
Pass |
pass |
| 3 |
Verify the mandatory values |
QueryID and SQL Statement should be mandatory attributes. If user tries to proceed without providing them, the appropriate error should be returned. |
pass |
|
pass |
Pass |
pass |
| 4 |
Add a new query with providing all the inputs correctly |
New query should be displayed under 'Queries' section with edit and remove options |
pass |
|
pass |
Pass |
pass |
5 |
Select 'Edit' icon of the new query |
The original values of the query should be displayed |
pass |
|
pass |
Pass |
pass |
6 |
Update the query and save it |
The updated values should be displayed |
pass |
|
pass |
Pass |
pass |
7 |
Go back to the first step and navigate again to the second step |
The updated query values should be persisted |
pass |
|
pass |
Pass |
pass |
| 8 |
Remove a query |
Query should be removed and the configuration preview should be updated with it |
pass |
|
pass |
Pass |
pass |
| 9 |
Select 'Add new Input mapping' option |
'Add New Input Param' popup window will be displayed |
pass |
|
pass |
|
pass |
| 10 |
Verify the mandatory attributes of 'Add New Input Param' window |
Name and SQLType should be denoted as mandatory. If user tries to proceed without providing them, the appropriate error should be returned. |
pass |
|
pass |
|
pass |
11 |
Select 'Edit' icon of the new input mapping |
The original values of the input mapping should be displayed |
pass |
|
pass |
|
pass |
12 |
Update the input mapping and save it |
The updated values should be displayed |
pass |
|
pass |
|
pass |
13 |
Remove an input mapping |
input mapping should be removed successfully |
pass |
|
pass |
|
pass |
14 |
I. Create a Query with an input mapping and save the data service
II. Invoke the data service with providing the necessary input parameters |
I. Data service should be deployed successfully
II. User should get the correct results |
pass |
|
pass |
|
pass |
15 |
I. Define an SQL statement with a stored procedure
II. Verify the mandatory INOUT type and Ordinal values of the input mapping |
INOUT type and Ordinal values are compulsory if there is an stored procedure |
pass |
|
|
|
pass |
16 |
I. Edit the SQL statement with removing stored procedure
II. Verify the In OUT Type and Ordinal values of the input mapping |
User should be able to save Input mapping without defining INOut type and ordinal values if stored procedure is not available |
pass |
|
|
|
Not tested |
| |
|
|
|
|
|
|
|
17 |
Select 'Add new output mapping' without entering 'Grouped by Element' |
'Grouped by element is required' error should be returned |
pass |
|
pass |
Pass |
pass |
18 |
Enter grouped by element, rowname and rowname space |
Valid values should be persisted successfully |
pass |
|
pass |
Pass |
pass |
| 19 |
Select 'Clear Result' option |
Output mappings should be removed |
pass |
|
pass |
Pass |
pass |
| 20 |
Select 'Add New Output mapping' option |
'Add New Output mapping' popup will be displayed |
pass |
|
pass |
Pass |
pass |
21 |
Select 'Mapping Type' as element, enter output field name and SQL column name |
New output mapping should be saved and listed in 'output mappings' table |
pass |
|
pass |
Pass |
pass |
22 |
Select 'Mapping Type' as attribute, enter output field name and SQL column name |
New output mapping should be saved and listed in 'output mappings' table |
pass |
|
pass |
Pass |
pass |
| 23 |
Select 'edit' option of an output mapping |
The original values of Output field name and SQL column name should be listed. Mapping Type should not be configurable in edit mode. |
pass |
|
pass |
Pass |
pass |
| |
|
|
|
|
|
|
|
| |
Data service wizard - Step 3 |
|
|
|
|
|
|
| 1 |
Select 'Add New Operation' |
'Add New Operation' popup will be displayed |
pass |
|
pass |
Pass |
pass |
| 2 |
Enter operation name and Query and save the operation |
New operation should be listed under operations table |
pass |
|
pass |
Pass |
pass |
3 |
Select 'Add New operation' when the query consists of input parameter mappings |
New operation popup window should have an option for 'operation parameter mappings' |
pass |
|
pass |
Pass |
pass |
4 |
Check mandatory values of add new operation screen |
'operation name' should be compulsory value |
pass |
|
pass |
Pass |
pass |
| |
|
|
|
|
|
|
|
| |
Edit Data service |
|
|
|
|
|
|
| 1 |
Edit an existing data service configuration |
Data service configuration should be displayed. so that user should be able to edit the configuration. |
pass |
|
pass |
Pass |
pass |
| 2 |
Edit a policy of a data service |
Updated policy should be persisted. |
N/A |
Edit policy page is not available |
N/A |
N/A |
N/A |
3 |
Edit data service if hotupdate=true |
Changes will be available after updating the configuration |
pass |
|
pass |
Pass |
pass |
| |
|
|
|
|
|
|
|
| |
Generate client |
|
|
|
|
|
|
| 1 |
Generate code with default code generation options |
The client jar should be generated successfully |
pass |
|
pass |
|
pass |
| 2 |
Generate code with wsdl 2
Write a client and invoke service |
Code generation should be successful
Service should be invoked successfully |
pass |
|
pass |
|
pass |
| 3 |
Code gen with unpack = true |
Code generation should be successful |
pass |
|
pass |
|
pass |
| 4 |
Code gen with unpack = false |
Code generation should be successful |
pass |
|
pass |
|
pass |
| 5 |
Generate code with XMLBeans |
Code generation should be successful |
Fail DS-172 |
|
Fail DS-172 |
|
Fail DS-172 |
6 |
Generate code with test cases |
Code generation should be successful |
pass |
|
|
|
pass |
7 |
Change the package name and generate client |
stubs should be generated inside a custom package |
pass |
|
|
|
pass |
| |
|
|
|
|
|
|
|
| |
Tryit tool |
|
|
|
|
|
|
| 1 |
Invoke a data service using Tryit |
Results should be displayed in Tryit page |
pass |
|
pass |
Pass |
pass |
2 |
Try it with changing endpoint to Soap11 |
Results should be displayed in Tryit page |
pass |
|
pass |
|
pass |
3 |
Try it with changing endpoint to http |
Results should be displayed in Tryit page |
fail DS-322 |
|
fail DS-322 |
|
pass |
| |
|
|
|
|
|
|
|
| |
Uploading data service |
|
|
|
|
|
|
1 |
Upload a dbs through management console |
The new dbs should be deployed successfully and listed in data services table |
pass |
|
pass |
Pass |
pass |
| 2 |
Upload an invalid archive |
error message appears |
pass |
|
pass |
Pass |
pass |
| |
|
|
|
|
|
|
|
| |
Service Statistics |
|
|
|
|
|
|
| 1 |
I. Select a data service and invoke it n times
II. Go to service management page and check service statistics |
Request count and response counts should be n. |
pass |
|
|
|
pass |
| |
I. Select a data service and invoke it n times. Do m no.of faulty invocations
II. Go to service management page and check service statistics |
Request count should be n. Fault count will be m. |
pass |
|
|
|
pass |
| |
|
|
|
|
|
|
|
| |
Transports |
|
|
|
|
|
|
1 |
Remove a transport from a service |
Transport should be removed from service and should not be able to invoke service with the removed transport. |
fail DS-330 |
|
pass |
|
pass |
2 |
Add the removed transport back |
Transport should be added to the exposed transports list of the data service and should be able to invoke service with the added transport. |
fail DS-330 |
|
pass |
|
pass |
| |
|
|
|
|
|
|
|
| |
Logging |
|
|
|
|
|
|
| 1 |
Select logging in the left menu |
"Logging Management" page should be displayed. |
pass |
|
pass |
|
pass |
| 2 |
I. Change the log level of the global log level configuration in to Debug
II. Do some activities and check console |
I. "Global Log4J Configuration successfully updated" message appears. Effective level of log4j loggers should be changed to DEBUG
II. DEBUG messages will be shown in the console |
pass |
|
|
|
pass |
3 |
Change the log pattern and update |
Messages should be logged according to the given pattern |
not tested |
|
|
|
pass |
4 |
Change the log4j appender to CARBON_LOGFILE and enter a log file |
log messages will be saved in the specified log file. |
pass |
|
|
|
pass |