1. Agile Testing experience (how detail is the story card, did u see the story card many times after it design?)
2. How to describe urself
3. Mobile testing experience, whether go to WAP or install the application
4. How to describe urself in three words
5. In which way u r going to improve urself
6. How to add value to ur team after u join
7. If there's 3rd party's error, how can u sort the problem and take ownership?
3.8 Distributed, Outsourced & Insourced Testing
In many cases, not all of the test effort is carried out by a single test team, composed of fellow employees of the rest of the project team, at a single and same location as the rest of the project team. If the test effort occurs at multiple locations, that test effort may be called distributed. If the test effort is carried out at one or more locations by people who are not fellow employees of the rest of the project team and who are not co-located with the project team, that test effort may be called outsourced. If the test effort is carried out by people who are co-located with the project team but who are not fellow employees, that test effort may be called insourced.
Common across all such test efforts is the need for clear channels of communication and well-defined expectations for missions, tasks, and deliverables. The project team must rely less on informal communication channels like hallway conversations and colleagues spending social time together. Location, time-zone, cultural and language differences make these issues even more critical.
Also common across all such test efforts is the need for alignment of methodologies. If two test groups use different methodologies or the test group uses a different methodology than development or project management, that will result in significant problems, especially during test execution.
For distributed testing, the division of the test work across the multiple locations must be explicit and intelligently decided. Without such guidance, the most competent group may not do the test work they are highly qualified for. Furthermore, the test work as a whole will suffer from gaps (which increase residual quality risk on delivery) and overlap (which reduce efficiency).
Finally, for all such test efforts, it is critical that the entire project team develop and maintain trust that each of the test team(s) will carry out their roles properly in spite of organizational, cultural, language, and geographical boundaries. Lack of trust leads to inefficiencies and delays associated with verifying activities, apportioning blame for problems, and playing organizational politics.
Common across all such test efforts is the need for clear channels of communication and well-defined expectations for missions, tasks, and deliverables. The project team must rely less on informal communication channels like hallway conversations and colleagues spending social time together. Location, time-zone, cultural and language differences make these issues even more critical.
Also common across all such test efforts is the need for alignment of methodologies. If two test groups use different methodologies or the test group uses a different methodology than development or project management, that will result in significant problems, especially during test execution.
For distributed testing, the division of the test work across the multiple locations must be explicit and intelligently decided. Without such guidance, the most competent group may not do the test work they are highly qualified for. Furthermore, the test work as a whole will suffer from gaps (which increase residual quality risk on delivery) and overlap (which reduce efficiency).
Finally, for all such test efforts, it is critical that the entire project team develop and maintain trust that each of the test team(s) will carry out their roles properly in spite of organizational, cultural, language, and geographical boundaries. Lack of trust leads to inefficiencies and delays associated with verifying activities, apportioning blame for problems, and playing organizational politics.
Agile
1)
Firstly, tester attend release planning and estimation, break down epic to story card. Then attend iteration (normally two weeks for one iteration) tick off, and working with BA to write Acceptance Criteria for each story card. Paring with developer when necessary to write automation test.
2)
when developer finish coding story card, he or she need to show tester what he has done which is call hand over.
3)
After that tester need to do exploratory testing against finished story card. If everything works fine, the final thing need to do for tester is show story to stake-hold (BA, business).
4)
By the end of each iteration, tester need to run regression testing as well.
Example:
-- story card --
As a Search Engineer,
I want to limit the number of results that are returned
So that too many results are not displayed that are not relevant to my search.
Firstly, tester attend release planning and estimation, break down epic to story card. Then attend iteration (normally two weeks for one iteration) tick off, and working with BA to write Acceptance Criteria for each story card. Paring with developer when necessary to write automation test.
2)
when developer finish coding story card, he or she need to show tester what he has done which is call hand over.
3)
After that tester need to do exploratory testing against finished story card. If everything works fine, the final thing need to do for tester is show story to stake-hold (BA, business).
4)
By the end of each iteration, tester need to run regression testing as well.
Example:
-- story card --
As a Search Engineer,
I want to limit the number of results that are returned
So that too many results are not displayed that are not relevant to my search.
Testing Exp with Dave
one question
"• Ability to manage multiple tasks in the order of importance and relevance to the business"
if someone ask me how to manager ultiple task
what i should reply
Dave says:
very important. "Prioritisation"
GRACE says:
according to what
then which one is high prirotiy?
Dave says:
it's more test manager level that needs to do that. You always have competing interests. The important thing is that you keep people informed of priorities
GRACE says:
ok
Dave says:
but generally, at Freshtel for example, critical production issues were always highest priority, especially billing related issues
GRACE says:
yep
Dave says:
Then for projects, there was constant discussion about which were the highest priority
These depend on the companies strategic direction
so for ftel, mobile projects were high. But so were TEsco projects
GRACE says:
ok
excellent answer! thanks Dave
Dave says:
what made it hard was the Sales guys always wanting stuff done at the last minute
coz they never planned anything or understood that small changes are not always easy
GRACE says:
Another question, for system test, what should be focus on ? different to UAT or regression?
find most of the bug ?
Dave says:
when they ask about UAT, you need to stress that you're testing from the end users perspective. So if there's any business requirements doco, you go back over that & understand what they want the system to achieve
system testing is from your perspective, knowing what it should do functionally but also how it's put together technically
never say "testing is about finding bugs"
that's a very simplistic view of it
"• Ability to manage multiple tasks in the order of importance and relevance to the business"
if someone ask me how to manager ultiple task
what i should reply
Dave says:
very important. "Prioritisation"
GRACE says:
according to what
then which one is high prirotiy?
Dave says:
it's more test manager level that needs to do that. You always have competing interests. The important thing is that you keep people informed of priorities
GRACE says:
ok
Dave says:
but generally, at Freshtel for example, critical production issues were always highest priority, especially billing related issues
GRACE says:
yep
Dave says:
Then for projects, there was constant discussion about which were the highest priority
These depend on the companies strategic direction
so for ftel, mobile projects were high. But so were TEsco projects
GRACE says:
ok
excellent answer! thanks Dave
Dave says:
what made it hard was the Sales guys always wanting stuff done at the last minute
coz they never planned anything or understood that small changes are not always easy
GRACE says:
Another question, for system test, what should be focus on ? different to UAT or regression?
find most of the bug ?
Dave says:
when they ask about UAT, you need to stress that you're testing from the end users perspective. So if there's any business requirements doco, you go back over that & understand what they want the system to achieve
system testing is from your perspective, knowing what it should do functionally but also how it's put together technically
never say "testing is about finding bugs"
that's a very simplistic view of it
TABLE 1.2 Testing principles
Principle 1: Testing shows Testing can show that defects are present, presence of defects but cannot prove that there are no defects. Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of correctness.
Principle 2: Exhaustive testing Testing everything (all combinations of is impossible inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risks and priorities to focus testing efforts.
Principle 3: Early testing Testing activities should start as early as possible in the software or system development life cycle and should be focused on defined objectives.
Principle 4: Defect clustering A small number of modules contain most of the defects discovered during pre-release testing or show the most operational failures.
Principle 5: Pesticide paradox If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new bugs. To overcome this 'pesticide paradox', the test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software or system to potentially find more defects.
Principle 6: Testing is context Testing is done differently in different dependent contexts. For example, safety-critical software is tested differently from an e-commerce site.
Principle 7: Absence-of-errors Finding and fixing defects does not help if fallacy the system built is unusable and d
Principle 2: Exhaustive testing Testing everything (all combinations of is impossible inputs and preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risks and priorities to focus testing efforts.
Principle 3: Early testing Testing activities should start as early as possible in the software or system development life cycle and should be focused on defined objectives.
Principle 4: Defect clustering A small number of modules contain most of the defects discovered during pre-release testing or show the most operational failures.
Principle 5: Pesticide paradox If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new bugs. To overcome this 'pesticide paradox', the test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software or system to potentially find more defects.
Principle 6: Testing is context Testing is done differently in different dependent contexts. For example, safety-critical software is tested differently from an e-commerce site.
Principle 7: Absence-of-errors Finding and fixing defects does not help if fallacy the system built is unusable and d
A complaint letter from real life....
Hello XXX
We trust you had an enjoyable weekend at ABC. Unfortunately there was quite a mess left after your departure on Sunday.
We were very disappointed to see the house left in a manner that was NOT in accordance with our tenancy agreement for which you signed to accept the terms. Is this how you leave your own house after entertaining?
The many bags of rubbish left on the front lawn were not disposed of, the yard was littered with beer bottles and food scraps from the BBQ and the BBQ itself was not cleaned at all and the hood cover broken with the screws left on the table.
Inside the house was worse.
Alcohol bottles left in all the bedrooms
Rubbish left on the floors as well as spills from drinks and food.
Furniture has been moved around all around the house and not placed back in position.
No dishes done and left strewn all over the benches and tables
No beds made
Lights left on in bedrooms
Back door left wide open after departure
There was not even as attempt to straighten the furniture or even make the house look half presentable on departure. You simply got out of your beds and walked out the door.
Due to your irresponsible behavior and obvious disregard and disrespect for the property and the incoming guests we will be deducting the cost of excess cleaning and rubbish removal from your bond.
We will be advising the cost of cleaning, rubbish removal, and repair of the BBQ hood in email to follow.
Regards
YYY
Property Manager
We trust you had an enjoyable weekend at ABC. Unfortunately there was quite a mess left after your departure on Sunday.
We were very disappointed to see the house left in a manner that was NOT in accordance with our tenancy agreement for which you signed to accept the terms. Is this how you leave your own house after entertaining?
The many bags of rubbish left on the front lawn were not disposed of, the yard was littered with beer bottles and food scraps from the BBQ and the BBQ itself was not cleaned at all and the hood cover broken with the screws left on the table.
Inside the house was worse.
Alcohol bottles left in all the bedrooms
Rubbish left on the floors as well as spills from drinks and food.
Furniture has been moved around all around the house and not placed back in position.
No dishes done and left strewn all over the benches and tables
No beds made
Lights left on in bedrooms
Back door left wide open after departure
There was not even as attempt to straighten the furniture or even make the house look half presentable on departure. You simply got out of your beds and walked out the door.
Due to your irresponsible behavior and obvious disregard and disrespect for the property and the incoming guests we will be deducting the cost of excess cleaning and rubbish removal from your bond.
We will be advising the cost of cleaning, rubbish removal, and repair of the BBQ hood in email to follow.
Regards
YYY
Property Manager