Triple T

Finishing point of task is complex to report; as there is no specific time period to test the application, there is just completion time specified (module end/release date).

If some specified time is likely given from managers, there could be a few minor functional items omitted at that point of time taking in explicit major functionalities alone in the account.

Overall test execution will be specified in days but generally in a module base testing, it will be mentioned only in hours; as it’s easy to track-in. In some cases, the time specified for a module in job card will be adjustable.

If handful functionalities are there then it can be easily analyzed and tested well before the scheduled time. Task estimate is always a recurrence procedure.

In our test estimation, time consumption happens (double the time from the initial estimation) because of slippages (build delays & iterations) from incorrect estimation.

Apart from meetings, a project task is generally estimated half a day (or) a day (or) in hours. I can observe that we all have a pattern to manage our teams but strategy is identical.

Question: So what's "Triple T" ???
Answer: Triple T >>> "Task Taken Time"...

Testing always depends on Task and Time to make a software look like a Triplet...

CT scan

Ever since our apps are on the cloud, we need to think testing as the same.

Functional & Performance Testing Tool, Defect Tracking & Test Management Tool, Capture & Playback Tool, Regression Testing & Database Testing Tool will be provided by service in TaaS.

TaaS means operating Software Testing with a group of people and tools.

1) Main drawback in general cloud service is the security of the data.
2) Another drawback is when some data disaster happens; revival of data will be complicated.

In some testing services, the Cloud Testing package offers the opportunity to access Test Tools with the Test Environments from anywhere around the world.

[CT scan - Cloud Testing scan]
[TaaS - Testing as a Service ]

Testing the Tester’s Pulse!

Height of frustration when our “Project Manager”/ “Team Lead” ask the following statements.

1. Are you sure, you have tested and verified the functionality?

2. Speed up and complete the sanity/regression testing soon as we need to push the latest code into the production instance.

3. It’s just a ‘Change Request’, it will take an hour to test those changes.

4. Guarantee me that, there are no bugs in this tested build.

5. I have a Client Demo within an hour/today, so just have the tasks done. Need this to be in live within the specified time-frame.

6. Are you bored on testing this application repeatedly?

7. Come on/ Plan for Saturday, Sunday or Holidays to test the application.

8. I didn’t have time to read your bug report. Just examine by yourself and close it.

9. Close all the bugs today itself and give an ideal defect report which provides a clear info. (Instead of using the term Testing.)

10. Kindly communicate with developer team and plan accordingly for all the bugs you have posted on Defect reporting tool.

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.