Rubber Stamping Ideas in Software Testing

Rubber Stamping in Software Testing >> Re-Usability/Framework Usability in Automation.

1. The test scripts will be less expensive due to the better rubber stamping.
2. Modification to the test scripts won’t affect the test data.
3. Healthier rubber-stamping is attained only when the scripts are organized properly.
4. Open to any Test Tool.
5. Test cases can be performed with ample number of data when rubber stamping is fittingly used.
6. Simple script management.
7. Independent of Application under test and same script works for every level of testing.
8. Testing can be planned with/without AUT (Application Under Test).
9. It offers notable (Depends on type of framework).
10. Range of test scenarios can be executed by changing the test data in the external data (as most of us use xls file).

Error Code: (1719) Windows Installer

Yesterday, I tried to plugging-in my USB port with (my mobile with CPU) but there was an access error. Error Code: 1719 [The Windows Installer service could not be accessed.]

If you are getting this error, try the following; as it helped for me.

Sometimes, if the Installer service is disabled, you will get this error. You can turn it on by going to Start, then Run and typing in "Services.msc".

Then scroll down to Windows Installer and double-click on it. Set the Startup Type to "Manual" and click Start to start the service.

Try now... Hopefully your issue is resolved.

You can also start the service by going to Start, Run and type in net start MSIServer into the Run box.

Software Troubleshooting

◙ If software sucks, its sucks...that’s it! ◙

=> Stop writing bugs, Start writing superior code.
=> Dead test plans.
=> Developer who wrote the code for particular feature is actually a good tester. They are accountable for testing their own code.
=> Integration testing is where the testers scores points because normal testing can be done by development team. (Testing their individual functionality)
=> User's vision is what testing is. So study the domain & be that particular user.
=> Development team needs to focus on their own functionalities.
=> While bug posting, dev team need to give/provide reports on how/why the bug occurred/solved.
=> End-User never care about the tree, they care about the forest.

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.

Software Tester - Best Practices

As a Software test engineer, our important task is not only writing the test plans/test-cases & filing the bugs. We have few more apexes to be balanced with our testing effort. They are as follows;

(a)Performing a domain knowledge transfer (DKT) to the team with regards to the data collected.
(b)Analyzing how the issues can be sorted out in the code level review for application performance.
(c)Ordering test strategies & test selection techniques ought to be prioritized.
(d)Reviewing UX/UE documents.
(e)Scheduling the prerequisite for a project before the requirement scrutiny starts.
(f)Sheltering the success with the testing process/methodology which is been applied.

Software Testing Reviews

Inspection: It is a more methodical and careful type of peer review. Inspections are more effectual at discovering defects than the informal reviews.

Pair Programming: In Pair Programming, two developers work jointly on the same program at a single workstation and constantly review their work.

Pass About: It is a multiple - parallel check where several people are invited to offer observations on the product.

Peer Desk test: In Peer Desk check only one person as well as the manager examines the work product. It is a casual review where the reviewer can use defect checklists and some investigation methods to increase the efficiency of the code/product.

Team Reviews: It is an intended and structured approach but less official and less fussy comparing to Inspections.

Walkthrough check: It is an informal review because they typically do not follow a distinct procedure, do not denote exit criteria, require no management coverage and produce no metrics.

Response Time, Throughput and Utilization

(a) Response Time
Response Time is the delay experienced when a request is made to the server and the server's response to the client is received. It is usually measured in units of time, such as seconds or milliseconds.

(b) Throughput
Throughput refers to the number of client requests processed within a certain unit of time. Typically, the unit of measurement is requests per second or pages per second. From a marketing perspective, throughput may also be measured in terms of visitors per day or page views per day.

(c) Utilization
Utilization refers to the usage level of different system resources, such as the server's CPU(s), memory, network bandwidth, and so forth. It is usually measured as a percentage of the maximum available level of the specific resource. Utilization versus user load for a Web server typically produces a curve.

Buggy Application (or) Software ?

Question: Is your "Software/Application" diseased?

>>> Then there are a few causes for unhealthiness. They are as follows;

1. Breakdown in informational exchange.
2. Unrealistic development time-frame.
3. Deprived design logic.
4. Feeble coding ethics.
5. Lack of version control.
6. Less focus on documentation maintenance.
7. Infectious third-party devices.
8. Less attention on software repairs.
9. End-line Alterations.
10. Individual Traits.

URL(another place where my blog got posted) :: Application-Diseased

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

Automation & Mind

Automation testing started. What are all in my (your) mind?

· Is application stable?

· Need to analyze the requirement.

· What are the pages/modules involved.

· What manipulation happens to the data?

· What kind of framework need to be implemented?

· Need to improve in-depth knowledge of the domain.

· Will my framework applicable for web application?

· What are the field validations?

· Where is information stored in the database?

· Questions related to object handling in the application.

· Are the business rules that manage the process?