Software Testing Email Ids

This is an aged old method for testing purpose. For the guys who are novel for Software Testing, this blog post is for you guys.

We need ‘N’ no. of testing email ids while testing an application. No need of creating ‘N’ no. of Email ids.

> You can use only one Email id for mails and you can use that N no. of time.
--For instance, my personal id is ‘arrvind_nicky@yahoo.com’
--You can use the same mail as arrvind_nicky+01@yahoo.com, arrvind_nicky+009@yahoo.com (or) etc.
--We will be getting the mails to ‘arrvind_nicky@yahoo.com’

After email name and before '@yahoo/gmail/in.com', there needs to be "+" and any numbers.

Hope this will be useful for your testing purpose.

5 Whys in Software Testing

I hope all have heard about the 5 why methodology in general for a project. How it can be implemented in Software Testing?

5 Whys in Software Testing? What it intended for us? How does this be relevant to testing?

After production deployment, imagine that someone initially in your team locates a bug, your Project manager asks why this was not found earlier but he/she will tell someone to fix it then that issue will not be remembered as how it occurred. While focusing on a theme/topic, keeping questions in mind and assuming things is the dangerous segment of the requirement/development/testing phase. We hardly ask why an issue was reopened, where the issue was placed and whether some additional issues will occur because of the hot fixes. We need to get rid of the bugs. A good ‘Unit Testing’ could be a solution in this kind.

Conclusion: Keep asking WHY for most of the answers until you are satisfied. You will be satisfied with 4th/6th why. But try to avoid bizarre questions.

Have a great testing day.

5 C's of Software Testing Techniques

Context – Context is King of the testing cards.

· Software Testing is always context dependent.

· In general, for jointly operating environment, we need to have a clear context.

· When people work together, the main segment is the “Project’s Context”.

· It desires to be perfect. No matter what the format is, if context is not appropriate, all will lead to failure / fault.

Consistency – Consistency is Queen of testing cards.

· The consistency in Software Testing can be viewed as application’s effectiveness. It is consistent user experience.

· A consistent tester is a tester, who has a well-versioned test cases and test suite.

· Testing is a steady approach which helps the planning better.

· The text’s position and fonts in an application needs to be consistent in all the browsers.

Correctness – Correctness is Jack of testing cards.

· Correctness is the essential purpose of Software Testing.

· Correctness is to tell the right action from the wrong one.

· Validating the correctness with various inputs is what inspired to be testing.

· Primary correctness should take place as earliest possible which leads testing as uncomplicated.

Communication – Communication is Joker of testing cards pack.

· Communication plays a vital role in Software Testing.

· A tester should have strong communication skill, since your points need to be noticed.

· You should be able to express your views effectively with regards to the bug tracking.

· Communication operates as a chief mediator in traceability matrix as its aiding customer relationship management and commitment negotiation.

Company (or) Community – Company (or) Community is Ace of testing cards.

· Testing Communities/Testing Companies moves the Software Testing to next level.

· Through Communities and Companies, the students from schools & colleges know how important and elegant the Software Testing is. We can see 'N' number of individual companies for Software Testing nowadays.

· The Software Testing market offers huge opportunities for both pure plays testing as well as IT service companies.

· Testing companies & communities are initiating more conferences to make Software Testing the center of attraction in IT.

URL(another place where my blog got posted) :: 5 C's of Software Testing