Skip to main content

Comments

 

Java, like most programming languages, can include comments. All right, and comments are just basically text inside of your source code that the compiler doesn't see. Right, and there are really kind of just two general uses for comments. One is that it allows you to add human readable notes to your source code, right, it allows you to type things in the source code so that when you look at it later, or someone else looks at it, it's just leaving notes to understand what you were doing there. It's also useful for hiding source cool without deleting it. Maybe you're testing things out, so you want to just kind of take some things away and type some new stuff, or if there's something you don't want to anymore, but you think you want to do it again in the future, so comments allow you to take that stuff out so the content is in your source code, but the compiler doesn't compile it. There are three types of comments in Java. One, which is called line comments, and if you basically just put a double slash, basically the compiler ignores everything until the end of the line, and when I said by the end of the line. it's until you hit the Enter Key, the new line character. It's not like other statements where it relies on the semicolon, right. So, the compiler just skips everything until the next new line. Then what are called block comments where you use a slash star to begin the comment and a star slash to end it. So, the compiler skips everything between those notations. They can be happened in the middle of a line or they can span multiple lines. And the last kind is a special kind of comment called a Javadoc comment, which starts out slash star and then ends star slash. There's a utility called Javadoc that allows you to generate documentation using this special comment format. It allows you basically to write your code documentation right inside of your source code, and then when you run the JavaDoc utility, if you follow the appropriate structure in your comments, that utility will generate documentation right from the source code. The details of Javadoc are outside the scope of this course, but I've got that you URL up there on the screen for you, if you want to dig into Javadoc and learn more about it.

Comments

Popular posts from this blog

Key Points of Leading RPA Tools

Key Points of Leading RPA Tools Automation Anywhere(AA) Blue Prism(BP) UI Path Developer friendly tool RPA Term was invented by Blue Prism Extremely User Friendly Offers Front and Back Office Robots It is an Enterprise grade RPA Solution tool Implementation Speed is high Script based, More Programming Skills required Supports only Back Office robots Re Usability is more since various integrations available with different workflows Smart Recorder Option available Code Insertion is difficult and not user friendly Free Community edition (PDF’s, Videos available for FREE) AA Bots can deploy in Physical Front Office machines & Cloud Extreme control over activities (Object Creation, Coding etc.) Con is - No Coding Annual support cost and license cost is higher What is Best RPA Tool...

Types of Recording

Types of Recording: 4 types of recording modes are available Ø   Basic Ø   Desktop Ø   Web Ø   Citrix 2 ways of Recording Ø   Automatic Ø   Manual Basic – generates a full selector for each activity and no container, the resulted automation is slower than one that uses containers and is suitable for single activities. Desktop – suitable for all types of desktop apps and multiple actions; it is faster than the Basic recorder, and generates a container (with the selector of the top-level window) in which activities are enclosed, and partial selectors for each activity. Web – designed for recording in web apps and browsers (supported: Internet Explorer, Google Chrome), generates containers and uses the Simulate Type/Click input method by default. Citrix – used to record virtualized environments (VNC, virtual machines, Citrix, etc.) or SAP, permits only image, text and keyboard automation, and requires explici...

Defect/Bug Life Cycle

Bug Life Cycle: It is a cycle in which a defect goes through different phases during its lifetime The Journey of a Defect/Bug from its NEW (or Born/Found ) state to Close (or END/Fixed ) state, so this journey of a cycle is known as ‘ BUG LIFE CYCLE ’. We can also called it as ‘ DEFECT LIFE CYCLE ’ 1.        New:  When a defect is logged and posted for the first time. It’s state is given as new. 2.        Assigned:  After the tester has posted the bug, the lead of the tester approves that the bug is genuine and he assigns the bug to corresponding developer and the developer team. It’s state given as assigned. 3.        Open:  At  this state the developer has started analyzing and working on the defect fix. 4.        Fixed:  When developer makes necessary code changes and verifies the changes then he/she can make bu...