Author Archives: c-braley

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

In memory testing

I really enjoyed this blog because I had never heard of in
memory databases before this. They do however make sense to me. I had always
thought of databases as their own unit, but never really gave much thought to
an in memory one. The fast access for certain programs makes a huge amount of
sense and I can see the uses for them as he gave examples of routing tables and
event poster.
What was interesting is that I can see the use for things
such as router tables, but didn’t give much thought to the testing uses part of
it. Databases can be overwhelmingly large and when it comes to testing, I
imagine that that size comes with a cost, speed. In comes in memory databases
to the rescue. It drastically reduces the time to test because of the speed
that memory works at which in my mind can increase the output of the product
possibly.
I think that if I ever do a lot of testing this is something
that I may indeed try out. You can read more about it here:

http://www.martinfowler.com/bliki/InMemoryTestDatabase.html

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.

On bug prevention

I really enjoyed this blog. The main theme more or less was
can bugs be prevented? He goes on to talk about how in testing we go at the
software from many different angles looks for bugs, but just how often is it
that we actually think about preventing them and are they actually inevitable
and can they even be prevented in the first place? While bugs are inevitable he
believes that they can be somewhat prevented and after reading his blog I
believe he is right.
He goes on to explain the general things we can do about
prevention such as better communication, trying to make less mistakes in the
code, understanding the platform that is being worked on and the list goes on.
The main question he asks is this; What can a tester do to help with bug
prevention? Testing happens usually after the bug is already in place and it is
the then too late to prevent the bug right? Well maybe not. He goes on to say
that the testing and the results report can actually influence the teams
thought in some areas or things. He says, “For
example, something as ‘innocent’ as an email saying: ‘I’m planning some testing
of feature X and I wanted to make sure I’m not duplicating work on this. What
kind of unit tests have you done on this?’ can gently nudge coders to think
about unit-testing their code (and the bug prevention benefits that come from
writing code that is unit-testable in the first place).
I really enjoyed this blog as he
makes many good points and if I am ever in the tester role I will surely take
some of his points to heart.
You can read the full blog here:

https://offbeattesting.com/2016/12/13/preventing-bugs/

From the blog format c: /s by c-braley and used with permission of the author. All other rights reserved by the author.