3

You definitely want to smoke test on production. If there is an issue you want to know first. Automated tests should help there. Your payment system will probablly have a different account than your staging environment, so best to double check the whole process so you can sleep at night. As for the metrics, you need to have some mechanism to label the ...


2

Take a look at SonarQube. It has some good code complexity metrics. Since code complexity generally translates to test-ability, it will give you a good idea which areas of the code need refactoring. It also gives you some metrics on unit-test coverage. I find the historical aspect of this metric to be helpful. As code is added and/or refactored, I like ...


2

How about the PHP Mess Detector, it generates all kinds of metrics about the code. Although its focus is not test-ability I think cleaning up the "mess" will lead to much better testable code. Since its a rules based system and open-source you could add more rules that are test-ability specific, maybe its possible to borrow rules from other products.


2

If you are doing some kind of ETL of legacy data into a new system, then there are two main things to worry about. First that the ETL logic is wrong, you do not bring over all records you meant to or the transformations are not done correctly. Second that there is some kind of problem that causes a data loss. For instance that the source DB cannot handle ...


2

Depending on where you live and whom you work for, fake money transfers on a production system could have serious legal consequences. Same for undocumented money transfers between departments within the business. Consult the legal department in writing if you have one, otherwise your boss, regarding refunds/reimbursements and the necessary documentation. ...


1

I am also confused by the answers given. First of all I assume you or the author of the book has a typo "C" is incorrect, because during the implementation... should be "D" is incorrect, because during the implementation... The answer given for A and B does not really make sense, since it would indicate that test design is correct. ...


1

If a developer, tester or architect has a need to see the difference between an environment then adding something like this seems fine. Don't add it because you can, but only because you really need it. Personally I would make sure the URL shows which environment it is.


1

We have same situation in my project. As a tester we just navigates to payment page, and tries to submit with fake or no data and get valid validation error. In addition to that, we always test ‘Paid Signup in Production’ with real payment. I’m sure, your place someone has valid card to make payment and reimburse or submit credits based on the policy. Best ...


1

Since there was no tool to do what I needed, I wrote one. https://github.com/edsonmedina/php_testability


1

The CTFL material deals with only that part when the people think that the automation is the silver bullet. This topic is dealt together with the testing tools where the same attitude can be experienced. The CTAL-TTA deals with the automation part. There is a book about it written by Rex Black. Please, keep in mind that I have read these books a year ago ...


Only top voted, non community-wiki answers of a minimum length are eligible