Some Test thought.
Functional test for new development:
Divide to two stage:
i) Early test: test in each team's isolated dev env. those envs are regularly sync.ed.
Release test: each test analyst will be responsible for several test plan, which covered one or more new feature/requirement. So test analyst is a role, plan the test, design the test, execute the test, and report the test.
ii) Automation test for regression test:
i) Early test: test in each team's isolated dev env. those envs are regularly sync.ed.
Release test: each test analyst will be responsible for several test plan, which covered one or more new feature/requirement. So test analyst is a role, plan the test, design the test, execute the test, and report the test.
ii) Automation test for regression test:
A lot of automation test (UI and Unit) as gate checking.
Other test: Performance. Performance test.
Problem or challenge:
1. Each team/test analyst works alone, find error in their own domain. Cross domain error sometimes not caught.
2. The strict release date and predefine feature(most likely are promised to customer)somehow restrict the Agile development.
1. script failure, hardware failure, network failed, and the dependencies, database failure, or system crash due to ...... etc
Other test: Performance. Performance test.
Problem or challenge:
1. Each team/test analyst works alone, find error in their own domain. Cross domain error sometimes not caught.
2. The strict release date and predefine feature(most likely are promised to customer)somehow restrict the Agile development.
1. script failure, hardware failure, network failed, and the dependencies, database failure, or system crash due to ...... etc
1. I should not only test the CR, also think the theory behind it.
2. Figure out the integration test, and what is the start point for that.
1. Everyone talk test ability. it is fluffy, but something we can consider. Test invovle early, and give opinion.
2. DEV should give more support to tester
3. Tester close developer team as has to be in the development process.
4. Give part of QA work to tester.
5. More clear job definition to the test analyst, and need get more power.
What improve
A lot of CR patched to installation seems not related to any feature, or requirement. They just patched to test installation. This is very similar to the old way to work, where the new changes just patched, and I have problem to follow a lot of changes. for example, the automation has a lot of changes, and I have to adapt to these changes.
The categorization should be better. Indicate the error scope is difficult
Monitor the QA plan to feature relationship is very difficult. New requirement, and new CR attched to the Feature are not synchronized in a satisified manner.
Some error I do not who the right people to talk to.
The preious requirement is replaced by the late delivery
What to improve
- Should be familar with the whole environment.
- Get to know the configuration parameters
Comments
Post a Comment