Why do I develop a dynamic test libraries

[Joong-Hee Lee]

I have just come around to develop test libraries.

I've noticed test libraries could be developed in three ways; static library, dynamic library, hybrid library.

The concept of the static library is very straight forward to me.

Also, I could understand how I develop the dynamic library and hybrid library.

But, when do I have to develop the libraries in the way of dynamic or hybrid library?

Can you guys explain in what circumstances I have to develop the dynamic or hybrid libraries?

I need your insights please.

Thanks in advance.

[Pekka Klärck]

2015-06-29 12:19 GMT+03:00 Joong-Hee Lee <leejo...@gmail.com>:
> I have just come around to develop test libraries.
> I've noticed test libraries could be developed in three ways; static
> library, dynamic library, hybrid library.
> The concept of the static library is very straight forward to me.
> Also, I could understand how I develop the dynamic library and hybrid
> library.
> But, when do I have to develop the libraries in the way of dynamic or hybrid
> library?

Most of Robot Framework libraries are static and you may never need to
write dynamic or hybrid libraries. They can, however, be very useful
if you have the actual library/tool used for testing elsewhere and the
library you create for Robot can just delegate everything to it. A
good example of this approach is the Remote library [1] that is
basically a proxy for actual test libraries hosted by remote servers
it communicates with. The dynamic API can also be used if you want to
create your own way to construct libraries for Robot Framework.
JavaLibCore is a good example of this usage.

[1] http://code.google.com/p/robotframework/wiki/RemoteLibrary
[2] https://github.com/robotframework/JavalibCore

Cheers,
.peke
--
Agile Tester/Developer/Consultant :: http://eliga.fi
Lead Developer of Robot Framework :: http://robotframework.org

[Joong-Hee Lee]

Thanks peke.

You made my head clear.

2015년 7월 2일 목요일 오전 6시 16분 38초 UTC+9, Pekka Klärck 님의 말: