CareerCup

1. Calculation of taxes is often involved with more than 1 price attributes.
2. We need to know which attributes (like quantity, discount, base price etc) are involved in that calculation.
3. Once all the involved attributes are identified, verify if there are any validations or recommendations on these attributes.
4. Verify the calculation's logic.
5. Performing these steps will give the exact location where the error is occurring.
6. Now once this is fixed, first perform unit test on the fixed area.
7. After unit test, integrate this feature with all possible (or allowed) attributes/validations/recommendations for calculations.
8. Now try the negative testing and regression.

agree above.
1. Identity where goes wrong, how many pages，which category of pages is wrong.Is any problem with deliverying the result？
2. Find how the wrong result is caculated，the logic of caculation，which attributes or logic is wrong.
Running enough test case will find the reason.
Then，fix it.
Unit Test
Integrate Test
Regression Test.

Taxes are calculated based on zipcodes/ shipping address.
We must ensure taxware is on before begin the triage process
verify correct percentage based on zipcode is added to order total
verify tax percentage is changed when there is promotion is applied to the product ( which means item price would get altered)
verify any tax free promotion is applied to the order , so that no tax applied
verify order total, item price is consistent across all the application untill where order gets fulfilled . ( say xml file which carries order information across various application)

i think we can use exploratory/ad-hoc testing here to isolate the problem with calculation of taxes. or should be test the entire module for errors

1. Do localized testing for the fix
2. Regression testing for the module/fuunctionality

1) Check if the problem is consistent across some other category of products
2) Check if the problem is consistent across some products with different price range

These are some scenario to assure if problem is consistent throughout the site
1) check logs / traces if any for the function responsible for calculation. Maybe things are correct at back end and only while displaying its the problem.

using this if problem found, get it fix, unit test it, integration and followed by Regression

- find out the delta of code changes in the tax calculation module and see if recent changes have caused this.
- Find out ant related module changed just before the defect is reported.
- Fix
- Unit test
- Integration test
- Regression test

Do Exploratory testing.
Find out what is the actual problem.
Then do Unit Testing & Regression Testing.