Page 1 of 1
about adding images to test cases and impact on DB size
Posted: Mon May 05, 2014 7:54 am
by rims
Hello,
We started using Testlink since few days and we are wondering if we start using the copy/paste image feature in our Test case design. If images are stored in the database, then we could end up with a huge Database.
What is your recommendation to us?
For information: in few months, we'll be like 100 people using this tool, so DB can grow up quickly.
Thanks a lot in advance
Re: about adding images to test cases and impact on DB size
Posted: Mon May 05, 2014 7:01 pm
by fman
I do not like storing images on DB.
Do not know if copy/paste is only working solution when you use Rich Web Editor.
Off Topic: if you plan to have 100 users, it will be great if your company can think about supporting TestLink development (just think about amount of money ypu are saving on licenses)
Re: about adding images to test cases and impact on DB size
Posted: Tue May 06, 2014 7:02 am
by rims
I do not like storing images on DB.
>>>> do we have the choice? it's not the way Testlink is storing images?
Do not know if copy/paste is only working solution when you use Rich Web Editor.
>>>> do you recommend using the dedicated icon to add images instead?
Off Topic: if you plan to have 100 users, it will be great if your company can think about supporting TestLink development (just think about amount of money ypu are saving on licenses)
>>>> I totally understand your point, but I'm not the person that can take this decision. However, I will recommend it to my supervisors.
Thanks a lot for your help
Rim
Re: about adding images to test cases and impact on DB size
Posted: Tue May 06, 2014 5:32 pm
by fman
>>>> do we have the choice? it's not the way Testlink is storing images?
Yes read config.inc.php
>>>> do you recommend using the dedicated icon to add images instead?
do not know if things will change