Measuring/Billing database usage in StratosLive - Summery

This Article collects all the posts under the Measuring/Billing database usage in StratosLive.

My Job
WSO2 Data Services Server User Guide
Need to find I/O rates, bandwidth used by each Database user
Limiting The Resource Use
I continued
Suggestions and replies
Collecting and summarizing the captured data
Followed the BAM samples.
Do you need data to play with?
Prototype version 1
Prototype version 1 has to be verified.
1st Verification
OSGi Services
Publishing to BAM
Using OSGi console to debug things

[Break for Test Automation]

Back to the Frozen project
WSO2 Storage Server
The Inevitable Change
Strange things do happen
Using Hive Scripts to Analyze and Summarize BAM data
Difference between two time ignoring the date
Replacing for ntask(quartz-scheduler), using timer task
It is almost 'THE END'

Beginning the Test Automation

We got this order to freeze our current project and join the test automation project, which was lead by Krishantha Samaraweera. 23 of us were divided in to 2 groups and assigned two of our major products, ESB and GREG. I am in the GREG test automation team. Here we are using a test framework called as 'Clarity'. Clarity was wso2 built testing framework which can be used to test our own products. Clarity is still under development. I will talk more about this framework in one of my future posts.

All the tests that we are writing is submitted as patches to the public jira project 'Test Automation'. Our team lead take a look at that and apply them to the main trunk/branch as we are not having committer rights. I will elaborate more on this jira thing and patch submission in my future posts.

We have to adhere to the standard coding style that is used in wso2. I have posted on this matter earlir in this blog. How to use the style xml to configure eclipse. You can find that post here. We used the remote debugging that is available in the IDE to test or patches. You can find my article on remote debugging here.

This was a nice learning curve for all of us. We went through lot of training sessions and was informed with best practices when testing, which were great additions to our knowledge. And it was a new place I was in 59 branch and now I am in 58 branch. And I must mention that here the TT table is far better than what we had in 59. After all this is temporary, I will return to the 59 after this test automation thing is done.

Remote debugging with eclipce, for WSO2 Data service Server (will work for any server).

As I am working with RSS manager , it gave me some errors. Only way I knew to debug this is using print statements. But with sysouts I couldn't figure out the error. I had a small doubt whether one variable is not initialized. So need a way to check this, I found this remote debugging option which felt like home. It was like debugging a small app on the IDE.

This is how you can do it.

Go to debug configuration (just right click in the project Debug As>Debug configuration)

There go to 'Remote Java Application'

fill it like below

Run the server with given port as debug port

./wso2server.sh --debug 8000

put some breakpoints and you are good to go...