The Secret Diary of Han, Aged 0x29

twitter.com/h4n

Archive for March 2005

Re: We could delete the dcaft database altogether to free up more space.

Han said: We could delete the dcaft database altogether to free up more space.

What is the dcaft database?

Written by Han

March 17, 2005 at 17:57

Posted in Uncategorized

…the QA team will be decimated soon.

Decimate originally referred to the killing of every tenth person, a punishment used in the Roman army for mutinous legions.”

Written by Han

March 14, 2005 at 16:16

Posted in Uncategorized

Agile testing blog

Grig Gheorghiu has an interesting web log on testing in Agile development. Also contains a lot of good stuff on the two test tools I mentioned.

Written by Han

March 13, 2005 at 19:55

Posted in Uncategorized

Sourceforge Database disk was full

When I tried SourceForge today, it said it could not connect to the database. I looked at it, and the disk was full (again).

To fix it, I shut down oracle (/etc/init.d/dbora stop), edited /var/opt/oracle/oratab to stop the dcaft000 database from running. I then started oracle again (/etc/init.d/dbora start). Finally I removed the redo logs on the dcaft database. Disk space is now at 92%. We could delete the dcaft database altogether to free up more space.

Sourceforge is running OK again.

Written by Han

March 11, 2005 at 22:25

Posted in Uncategorized

Re: Test tools

These tools looks pretty good for validating the GUI. I haven’t tried to use them with Siebel yet, but I should have a chance next week. The toos that I looked into had modules specifically for Siebel 7, but are general purpose web app testing tools as well:

Quick Test Professional: This one is from Mercury–pretty much the industry leader in automated testing. It’s high end but is pretty easy to use. You train it by recording user actions as opposed to writing scripts (which is also possible). It has a Siebel option. There would be some learning curve involved. I looked at it a while back but I could never get a demo copy of the Siebel module from Mercury.

Empirix e-Test: Looks pretty cool. Maybe a little bit of scripting involved, but they advertise no coding. Has Siebel module. The suite comes with load testing and test case management tools as well. I’m going to look into getting a free trial.

Scriptmap: This one takes a little bit different approach. Says it uses requirements to drive the tests instead of recording user actions. The site is an interesting read. Looks like it is mainly geared towards Siebel–at least they spend most of their time talking about Siebel on the site.

Segue: Looks like if you buy the Siebel suite, you pretty much just get that. Says they are a Siebel alliance partner…

I’m going to try to download and test some of these if possible to see if they might be a good fit. I’ll keep you posted.

Written by Han

March 10, 2005 at 14:38

Posted in Uncategorized

Test tools

I searched around for useful testing tools last weekend. One reason is that the QA team will be decimated soon. After next week, it will basically only be Takagi-san and Xiaomei. Clearly, unless we have some automated test tools in place, QA will only be able to test a fraction of the developed functionality. I assumed we need the following:

  1. a browser UI testing tool
  2. a functionality testing tool

The main requirement for these tools is that the QA team can create new tests themselves without (much) coding, and that the tests are readable and self documenting.

There is quite a bit of good stuff out there. I found the following the most interesting:

Selenium

This is a tool for testing GUI’s. It works through a browser based Javascript framework, and takes its test cases from HTML tables. It works with IE and Gecko browsers. The nice thing about this setup is that, since it runs in the browser, it supports Javascript properly, which is where many other webtesting tools suffer. Plus it is free. I played around with it a bit and created a small demo test for the Operator portal. It supports multibyte properly. I haven’t tested it with Siebel yet. The tool does not need to run from the browser. It can also “drive” the tests from C# or Java code. But the browser-based mechanism seems the easiest to use.

A GUI testing tool is good at checking whether the GUI is in order, but it can test the underlying functionality only indirectly, through GUI actions. Therefore we should also use a functionality test system to test the logic. I had a look at the following tool.

FitNesse

Like Selenium, FitNesse uses HTML tables that contain the test cases. FitNesse is also a Wiki, so that it is really easy to add and change the testcases from within the framework. In contrast to Selenium, it needs some development support. Some glue code (”fixtures”) is necessary to connect the HTML tables to the code to be tested. But once the fixtures are written, tests can be added very easily, and the overall result is a set of automatically executing, nicely documented functional test cases. This tools supports both Java and C#.

Written by Han

March 9, 2005 at 19:23

Posted in Uncategorized

Lunaris reanimated

Lunaris is back in the land of the living. Booting into safe mode and running a chkdsk on C: did the trick. The drive has plenty of empty space, so that is not the problem. We restarted Siebel to get that to work again.

C. will migrate the Siebel DB to a Solaris 9 machine. This means the Siebel DB will get more stable, and we free up another G2 for development work.

Written by Han

March 9, 2005 at 18:54

Posted in Uncategorized