gowan

And that identity would be otaku?

Welcome to the N.H.K. is an anime that explores Hikikomori.

minor nitpick:

Prolog does not have functions. It has functors/predicates.

Unlike functions there is no distinct set of inputs and outputs. In prolog you can solve car(Foo,Bar):-some_rule. for Foo or Bar.

Prolog is great at modeling complex logic.

As an Automation Developer I use Prolog (swi-prolog) to generate test cases for some of the systems I test. In paticular I use prolog to model the high level buisness rules. This would be an example of an "expert system".

RedHat is supporting docker via OpenShift[1] so I don't see docker dying anytime soon. From my limited experience docker support on CentOS/RHEL 7 is very good.

[1] https://www.openshift.com/products

Ruby (MRI/JRuby) are gaining traction in automated testing at large enterprises. Ruby is easy to learn and integrates well with java.

Cucumber provides better reporting than JUnit/TestNG. For web testing you have watir. For SOAP services you have savon which IMO is much easier than SOAPUI. For RESTful web services you just make direct calls. Then there is sikuli for ad hoc GUIs.

My wish list:

* reproducable build for docker images

* generate randomized test cases for web flows

Ruge looks interesting but the last commit is November 2013. Is the project still active?

Ruge is dependent on SICStus Prolog[1] which is proprietary. Has anyone had success running ruge on an opensource prolog such as GNU Prolog, swi-prolog, or yap?

[1] http://bmccarthy.bitbucket.org/ruge/download.html

author here:

Yes, this example is simple. IMO it's best to introduce people to what they are familiar with. I didn't want to write an example that demonstrated the full power of prolog but lost 90% of the crowd. My hope was that this would spark curiosity in how prolog can be used to generate test cases.

At the moment I'm using the technique in the post to generate happy path test cases for an application with lots of buisness rules.

I have a few docker containers I use as a testing environment. I ended up mounting gems from the host. They where mounted from a /tmp dir so docker would not pollute the gems on the host.

I think your understating how hard it is for a beginner to create a spec for an rpm. As a n00b I recently did this for sikuli on CentOS 6. The macros in the spec file gave me the most trouble. The close second was the build process until I realized that specs where designed for maintainers not developers.

Normally, someone has already written a spec that you can modify for your use case.

Given the number of docker projects (looking at you redis) that build from source, docker seems to be moving into package management.

Nice to see sikuli on the front page. I'm currently using it to test a legacy application.

Sikuli is good at image matching. For me sikuli broke when I started to take images of text. The font would render differently in gnome and the vm (vncserver/twm) jenkins ran the tests on. I ended up creating docker images of the test environemt so the docker image would be the same on jenkins and the testers machines.

Debian has a sikuli package libsikuli-script-java and sikuli-ide. I've also written a docker file for sikuli on debian wheezy [1].

[1] https://github.com/jesg/sikuli

There are plans to build a desalination plant in the Bay Area [1]. This and other plants in CA could help water supply in populated areas.

The water districts in CA have two problems: 1. They are not connected well so water cannot easily be transfered from one district to another. 2. The reservoirs cannot sustain an extended drought.

[1] https://portal.ebmud.com/our-water/water-supply/long-term-pl...

Send a command to display 1.

`xterm -display :1 -e <command>`

This is useful when running automated tests on top of vnc.