Jump to content

Recommended Posts

Hello all,

 

Got a question for all the experienced members out there.

 

I am doing some work for a department at my university which involves updating their database system implemented using PHP + SQL. My job is to implement new features /  correct broken features etc.

 

Now my question is when i implement new feature (lets say a new search parameter) how can i code some test cases to make sure it works fine on its own and also in conjunction with the existing parameters ? can i somehow automate the process ?

 

I fairly comfortable with php but never dealt with a system of this complexity and manual testing tends to be slow and error prone. and i am fairly new to automated testing.

 

Regards,

ankitmcgill

Link to comment
https://forums.phpfreaks.com/topic/163289-php-test-cases/
Share on other sites

Now my question is when i implement new feature (lets say a new search parameter) how can i code some test cases to make sure it works fine on its own and also in conjunction with the existing parameters ? can i somehow automate the process ?

 

Typically you would do it manually - at least I would. But remember, after you go through and check everything once or maybe even twice, then open it up to a group of users to 'beta' test it. You could automate the process, yes, but that would seem like more trouble than it is worth.

Link to comment
https://forums.phpfreaks.com/topic/163289-php-test-cases/#findComment-861615
Share on other sites

kingphilip, thanks for the reply.

 

the problem is that i am the only developer on the system and the system is already in usage. to add to the problems the people using the system are psychologists and hence not very computer savvy. in effect it falls on me to make sure the new feature works before making it available.

 

for small things its easy enough to do manual testing to make sure it does not break anything but for cases where you have complex SQL queries being done i felt the need for more full proof solution.

Link to comment
https://forums.phpfreaks.com/topic/163289-php-test-cases/#findComment-861658
Share on other sites

Use a CVS (Concurrent Version System) to track your changes.

Use a copy of the live site to do your testing.

Backup the live site before you make any changes.

Test the changes on the live site.

If it doesn't work, restore the backup.  If it does work, celebrate.

? ? ? ?

Profit.

Repeat

Link to comment
https://forums.phpfreaks.com/topic/163289-php-test-cases/#findComment-861661
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.