Posts

Showing posts from June, 2016

"STRIVING FOR ZERO BUGS ON THE TEST ENVIRONMENT"

Image
https://testhuddle.com/resource/striving-zero-bugs-test-environment/ Big overhead in raising bugs,  Solution:  Requirement over Solution, use BDD and check requirement early.  Story should be as small as possible, and big enough to test. Slice the story is important. A story should be Deliverable, Testable, and Delopyable.  Clear as much as possible in beforehand.  Keep update from Developer Think why not prevent the bug. 

Process Change

Image

New BackTech by 2020

Image
Open API to the new trend, Bank will learns more about how outside doing by open their API. IoT + BlockChain

Future Test roles

Image
Old roles in Testing The roles in testing has been changed a bit when Agile come

Hans Buwalda - "How to get automated testing done"

Image
https://testhuddle.com/resource/how-to-get-automated-testing-done/ Few slides from Hans Buwalda's presentation "How to get automated testing done". It is a very good presentation, summarized many good points of test automation.

The quadrant of Automated Test

In M.B's blog he talks about the automated test, and programmed test.  I just think, it might be a good idea to categorize the automated test, so that an "Test automation" engineer will easily find their place in the figure, also find out what competence that he lacks. So I create a simple quadrant, very basic draft https://goo.gl/pyox70

Take aways from today's "Self-Organized Organization" meet-up

Competence :  Nothing new, people need that to do well in their work.   Autonomy :  Yes,  human being like the feeling that they can control their work or life. A kind of comfort zone.  Relatedness :  New, the relationship in the work is very important, people gain more when they feel they are related.  Control the periphery : Yes, also give the confidence to their work  Clarity of purpose :  Important but not know,  the WHY is always the most important to the work, this is the only way to convince everyone in the team to contribute.  Cocreating the task over a blueprint ,  very agile way.  being a human being over being an expert :  it is a team.  Relatedness over execution  : repeat the relatedness in the work Asking over telling  :  Ask, cooperate, instead being a commander.  Job description vs role :  in the agile (not software agile) organization, only have a role, everyone can be that role, and the organization should be able to adapt the the change or r