Friday 21 September 2012

Developer vs Tester (fake competition)


Developer vs Tester … a never lasting debate..i know..

Today in lunch table, I faced a weird situation when one of my team members forced me to contribute my thoughts regarding Developers vs Testers; actually they wanted to show that the Developer is betters than the Testers. Their point, whatever I got, was the Developers are more creative, innovative and knowledgeable than the Testers (Developers point) and Testers are more responsible, dedicated and detail oriented (as Testers said). Well they provided a lot of stuffs, examples and evidences to prove them-self right. Ahhh…… again that fake competition.



I tried a lot to let them understand that we cannot judge the Head and Tale in same Coin. Both have their own roles and responsibilities. But the people had childish ego to prove them-selves superior.

I, truly, never understand why such intelligent, capable and talented people fall in such a waste topic to discuss. I mean there is lot of issues, topics are there to discuss of. Why they want to prove themselves perfect? I mean we guys are in same team, on same project and doing the same task so where’s the point of discussing superiority?

At last, I just added few things before leaving the table; the IT industry is like a Football game where Developer, Business analyst etc are the Strikers, Quarterback...and Tester is like Goal Keeper. The whole team plays hard to win the match and I understand even the Development team is concern about the Quality but if Goal Keeper misses a goal, the whole team is going to lose. Even same for the developer as the Developer has his own responsibilities as they must strike a goal otherwise Team will also lose. So where’s the Competition buddy? It’s a Team work dude.



So instead of comparing the foolish things(because both the developer and tester are on the same boat), let unite to build a better world.

Thanks God, whatever I used is already developed and tested J


Friday 7 September 2012

Install Android Apps to SD Card (by Default)

By installing apps directly to SD card, we can overcome the problem of internal memory of devices (applicable for those apps which are not dedicated for internal space). But the question is 'how to set storage default to sd card' ? So here is the solution:


Pre-requisites:
1. Android SDK (Click here for SDK setup)
2. Setup of ‘adb’ (Click here for adb)



As we know, Android apps install to the internal storage by default, but we can also set the SD card as the default install location. This trick allows moving almost any app to the SD card(WITHOUT Root Access required).

This requires Android 2.2 or later. To change the default install location, you’ll need to use the ADB (Android Debug Bridge) and Android SDK.


Step 1: Enable USB Debugging-
First, we need to enable USB debugging on Android device. For this:

Open the Settings screen > tap Applications > select Development




Then, tap ‘USB Debugging’ checkbox to enable it. This will enable debug mode, allowing changing the settings on Android device from computer. We may want to disable debug mode after completing this process.





Step 2: Install the Android SDK-
All we need to download and install Android SDK on computer.
After installing the SDK, launch the SDK Manager from Start menu



The ADB utility isn’t installed by default. It’s included in the Android SDK ‘Platform-tools’ folder – select this package and click the Install button to download and install it.



After the process completes, connect Android device to computer with its included USB cable (or just connect the emulator). Windows should locate the device and install the appropriate drivers automatically. If it doesn’t, you may have to download and install the appropriate drivers from your Android device’s manufacturer. Do not mount the device after connecting it – just plug it in.


Step 3: Using ADB-
Open a Windows Explorer window and navigate to the ‘android-sdk\platform-tools folder

Note: platform-tools folder install with the package of SDK.

Path could be as : E:\android-sdk-windows\platform-tools


Launch a Command Prompt window in this folder by pressing and holding the Shift button, right-clicking in the folder, and selecting Open command window here.




Run the adb devices command, it will show the connected Android devices:




Run the following command to set the default install location to your SD card:

adb shell pm setInstallLocation 2


Note: If you want to revert this change later and install apps to the internal storage by default, run this command:

adb shell pm setInstallLocation 0

0 represents device’s internal storage, and is the default. 2 represent the external storage, whether it’s an SD card or USB storage.



Moving Apps to SD Card:
Apps that refused to leave your system storage can be moved to the external storage. For instance, below you’ll see screenshots of the Slacker Radio app. Before the change was made, the ‘Move to USB Storage’ button was grayed out (disabled). After the change was made, the button is enabled and the app can be moved.


To move an app to the SD card, open the Settings screen, tap Applications, and select Manage Applications. Select the app you want to move and tap the Move button on its details screen.

Monday 3 September 2012

Validation and Verification


Verification: 

  • Definition: It is a static testing that mean testing a product without executing it (through Walk through, Inspection and Review etc). It helps in finding out the defects with the location of defect. It is a process oriented.
  • Key Objective: Are we building the product right?
  • Evaluation Item: Plan, Requirement, Design, Code, Test Cases etc)
  • Activity: Review, Instection, Walkthrough


Validation: 

  • Definition: It is a dynamic testing that mean testing a product by executing it (through Integration testing, System Testing etc). It helps in finding out the defect only and not its location. It is a product oriented.
  • Key Objective: Are we building the right product?
  • Evaluation Item: Actual Product, Software
  • Activity: Testing


Well we can understand this as Verification is done through out the life cycle of the project/product where as validation comes in the testing phase of the application.

Severity and Priority


There are lot of confusion faced by beginners between Priority and Severity. Well, both the terms Priority and Severity are used in Bug Tracking in order to mention the importance of that bug to development team.

Severity: deals with the functionality of application
1. Severity status is used to explain how badly the deviation is affecting the build.
2. Severity type is defined by the Tester based on the written Test Cases and functionality.

Priority: deals with the customer requirement
1. Priority status is set by the Tester in order to let Developer know the time frame to fix a defect. If High priority is mentioned then the developer has to fix it at the earliest.
2. Priority status is set basd on the customer requirement.

Example: 

1) High Severity And Low Priority: If any application crashes after multiple use of any functionality (e.g. save Button use 200 times quickly then that application will crash)

Means High Severity because application chrashed but Low Priority because no need to debug right now you can debug it after some days (as its not a valid scenario because user is not going to click save button 200 times quickly)

2) High Priority And Low Severity: If any Website say "Yahoo" now if the logo of site "Yahoo" spells as "Yho" than Priority is high but severity is low.

Here the functionality of website is ok but it effect the name of the website so important to fix it quick ---Priority