http___blog.teamgrowth.net_index.php_bg_tag_software-testing-and-quality-assurance-blogs-and-information_1.xml
http___blog.teamgrowth.net__4.xml
1.1 2.1 3.1 4.1 5.1 6.1 7.1 8.1 9.1 10.1 11.1 12.1 13.1 14.1 15.1 16.1 17.1 18.1 19.1 20.1 21.1 22.1 23.1 24.1 25.1 26.1 27.1 28.1 29.1 30.1 31.1 32.1 33.1 34.1 35.1 36.1 37.1 38.1 39.1 40.1 41.1 42.1 43.1 43.2 43.3 43.4 44.1
Преводач Последните публикации - Как да се повтаря на заглавните редове на всяка страница в Reportviewer (RDLC)? - Как да се интегрират на Google Maps във вашия сайт? - Как да напишете съдържание за вашия уеб сайт за привличане на повече потребители - Как да създадете уеб услуга в PHP - Автоматизирано тестване на инструмент QTP (Quick Test Professional) Скорошни коментари Архиви Категории NET - Андроид - Apache - API - Cloud Computing - Data Center - База данни - Светкавица - Google Хром - HTML - Често Задавани Въпроси - Linux - Разработка на приложения за мобилни устройства - MySQL - Open Source - Perl - Photoshop - PHP - Програмиране - Прокси сървър - Осигуряване на качеството и изпитване - Търсачка за оптимизация - Сигурност - Съхранение - TeamGrowth - Инструменти - Настойнически - Уеб дизайн - Xen Meta Tag Архив: софтуерното тестване и за осигуряване на качеството, блогове и информация Разлика между осигуряване на качеството, тестване на софтуер и контрол на качеството Качество: качество "означава последователно отговаря на изискванията на потребителите по отношение на разходите, графика на доставка и сервиз. Осигуряване на качеството (QA): - QA е планиран и систематичен начин за оценка на качеството на процеса, използван за производство на качествен продукт. - Целта ... Продължавам четене Tagged difference , Quality Assurance , Quality Control , Software Testing , software testing and quality assurance blogs and information Leave a comment Публикувано в осигуряване на качеството и тестване Маркирани разлика , за осигуряване на качеството , контрол на качеството на софтуерното тестване , софтуерното тестване и за осигуряване на качеството, блогове и информация Оставете коментар
1.1 1.2 1.3 2.1 4.1 4.2 6.1 8.1 9.1 9.2 11.1 13.1 15.1 17.1 19.1 19.2 21.1 21.2 23.1 23.2 25.1 25.2 25.3 25.4 26.1 27.1 27.2 27.3 27.4 27.5 28.1 29.1 30.1 32.1 33.1 33.2 34.1 35.1 36.1 38.1 39.1 40.1 41.1 42.1 43.1 44.1 45.1 46.1 47.1 47.2 48.1 48.2 49.1 50.1 50.2
Perl is a powerful, adaptable and dynamic programming language which is compiled each time before running. It was first developed by Larry Wall in late 1980s. Today we will discuss briefly the system variables used in Perl. The following are system variables used in Perl: This variable returns the process ID of the process that is running the current Perl script. It is very handy where the operations are to be performed using the script’s process ID. This variable returns the user ID of the current process. This variable returns the effective user ID of the current process. Note: The difference between current and effective user is that effective user is running with the privileges of that user id. Basically the real is the user id of the user and current is the process that started you. This variable holds the real group ID of the current process. This variable holds the effective group ID of the current process. This variable holds the name of the file the current Perl process is executing. This variable stores the interpreter path or the binary of Perl that got executed. This variable is very helpful to get the version number of the perl interpreter. This helps to trace the version compatibility issues that occur with various modules. The name of the operating system the Perl code was built on. This is similar to $Config{‘osname’}. This variable returns the time at which the script was executed. This time is in seconds since the beginning of 1970. Returns the value of the warning switch. It is either TRUE or FALSE. Warnings is a Perl program to control additional Perl warnings. The syntax to enable a warning is to “use warnings” and to disable them is “no warnings”. %ENV This special hash variable maintains all the environment variables. Basically environment variables are used to store the information that is used to run the system/computer. One can change the values of these variables but these changes are available within the program. Once the program exits, these changes loose their respective scope. Every Perl process is provided with a copy of these environmental variables. One can print out all these environment variables using: foreach (keys(%ENV)) { print “Key:$_ and its value: $ENV{$_}\n”; %SIG This is also a special hash variable that can be used to set signal handlers of various signals. This makes signal handling quite easy as one can set a signal handler to a certain value and again reset its value to default. Similar to %ENV, %SIG can also be printed using: foreach (keys(%SIG)) { print “$_”; My system provides the following list of signals: NUM63,TRAP,NUM42,URG,STOP,NUM39,NUM62,NUM43,USR2,NUM57,NUM56,RTMAX,NUM59,VTALRM,CONT,NUM45, NUM61,TERM,NUM44,NUM36,NUM32,BUS,NUM40,NUM51, IOT,STKFLT,NUM41,KILL,QUIT,NUM37,NUM50, ABRT,NUM48,CLD,NUM35,NUM38,TTOU,IO,TSTP, PROF,NUM53,NUM58,SEGV,RTMIN,POLL,PIPE,SYS, NUM46,PWR,CHLD,HUP,FPE,NUM54,XCPU,TTIN,NUM52, NUM55,XFSZ,NUM33,INT,NUM49,UNUSED,WINCH,USR1,ILL,ALRM,NUM47,NUM60 @INC This special array is similar to shell’s PATH variable. Although, PATH contains a list of directories that are to be searched for executables, @INC contains a list of directories from which Perl modules and libraries can be loaded. When we code use()” or require() or do(), Perl searches the list of directories from @INC and searches the requested file in this array. If the file is not present then one has to define it separately. %INC This is special hash that is used to store the names of the files and modules that were successfully loaded and compiled for a given Perl script. Before loading and compiling any file or module Perl initially checks for its availability in this special hash and thus if not found loads and compiles it accordingly.