Simple but effective Test report template

It would be easier for us to track the bugs or test scenarios that you found or tested, if you could present that in the form of table with pass/fail status and feedback/remark.

So you can make use of the below template for accumulating or sharing the test result.

Sr. No.	Test Scenario	Expected Result	Actual Result	Status (Pass/Fail)	Remark
1
2

Comments

Unlock protected blocks in Siemens SIMATIC Step 7

Recently I'd been called by Hindalco's Fabrication Plant division to unlock the protected blocks in Siemens SIMATIC Step 7. They were in need to unlock those blocks since an year because of 1 million Rupees of loss per month. They want to re-program those blocks but it was locked by the man who'd done the setup. From the people working in that department, I came to know that they were trying to call that man (someone from Italy) right here but he's not coming. Actually, what he'd done was that he'd locked some of the blocks and deleted the source file. And Siemens didn't provide any feature to unlock. Department people also told me that even the people working in Siemens don't know how to do it. Being a software engineer I know that any thing can be reverse engineered. So I took up the challenge. How did I unlocked the blocks? The first thing I'd done was searched about this software at Google and read about what is this software all about. Aft

JS: The complete code example of Crypto.js (DES)

For one of the project I was trying to use crypto.js but I found that the Quick-start Guide have some deficiency in terms of library usage. So I am writing it here as a useful note for memory recap. <script src="http://crypto-js.googlecode.com/svn/tags/3.1.2/build/rollups/tripledes.js"></script> <script> var encrypted = CryptoJS.DES.encrypt("The secret message", "secret_key"); var e_msg = encrypted.toString(); console.log(e_msg); var decrypted = CryptoJS.DES.decrypt(e_msg, "secret_key"); var d_msg = decrypted.toString(CryptoJS.enc.Utf8); console.log(d_msg); </script>

How to convert JIRA story into sub-task or defect?

Many times we entangled in the situation where we have made a story in JIRA but later on realised that it should have to be defect or in other case, sub-task of another story . Story → Sub-task So the workaround for converting the story into defect is given below: Open your story Click on more option Click on the Convert to sub-task option in the dropdown You would be asked to choose Parent story, so chose relevant story After submit, your story gets converted into sub-task Story → Defect Now if you want the story to be converted into defect, then you should first convert it into sub-task. Thereafter, you can convert that sub-task into defect as given below: Open the sub-task Click on more option Click on the Convert to issue option in the dropdown You would be asked to fill up relevant fields required for raising a defect , fill them up as required After submit, your sub-task gets converted into defect .

Voila!

Search This Blog